Anastasia Mavridou

Hi Alexander, what you describe fits perfectly with the idea of FRET templates: you could create a template for a type of requirements and then have placeholders for identifiers (X1,...

I see what you are saying. Another way of describing such constraints in a concise way is through a quantified (first-order) logic formula. For example: "FSM shall always satisfy forall...

Hello Alexander, The import feature of the Variables Mapping panel is used for importing model architectural information (e.g., Simulink input and output signals) in order to map these with the...

Hi @ahmedwaqar, thanks for your suggestions. We are currently working on extending the export/import functionality of FRET so this is good timing. Anastasia

Yes. We have added export to CSV format. It will be included in a future release.

Similar issue: Pouchdb does not run on Apple M1 architectures. To run it we need leveldown version ^6.0.3 but pouchdb requires leveldown version 5.6.0 (as listed in the package.json file).

We have added this in FRET v3.0! Instructions of how to import/export variables are written here: https://github.com/NASA-SW-VnV/fret/tree/master/fret-electron/docs/_media/user-interface/exportImport I am closing this issue.

Yay! We would love to receive your feedback.

This is included in release v3.0. I am closing the issue.