Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

specifiying an exporter with -e causes an error - if no exporter is needed. #80

Open
markus-stoll opened this issue Sep 20, 2014 · 6 comments
Assignees

Comments

@markus-stoll
Copy link

Running pure post-processing example should not crash, if an exporter was specified with the -e parameter.

This would allow easier automatic testing.

@wadoon
Copy link
Member

wadoon commented Sep 20, 2014

The BaseExporter aka -e base should be your friend if you want a dummy exporter.

ps. If there is no exporter execution, then there is no the simulation output in the memory. Hence the post-processing fails.

@markus-stoll
Copy link
Author

Yeah but how to decide if to use -e base or -e sofa when you run several MSML files for testing?

The simulation output is not needed in memory - the post processing is only using file data.

@markus-stoll markus-stoll reopened this Sep 20, 2014
@wadoon wadoon closed this as completed Sep 20, 2014
@wadoon wadoon reopened this Sep 20, 2014
@markus-stoll
Copy link
Author

sorry for opening/closing... What we could need here is a check, if the simulation run is really needed before trying to start the simulation with an empty description.

@wadoon
Copy link
Member

wadoon commented Sep 20, 2014

Then this not post processing (in the sense, it is executed after the exporter)

@markus-stoll
Copy link
Author

yes but in the sense of processing already existing simulation results. The same problem occurs if you only have preprocessing operators.

I think the using the -e exporter parameter should not enforce that a msml simulation has a scene included.

@markus-stoll
Copy link
Author

exporter should also work without a defined scene.
A warning should be displayed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants