-
Notifications
You must be signed in to change notification settings - Fork 7
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
[batch legacy] Add the possibility to run directly an experiment #361
Comments
This could be a good idea, but not using the XML file. As the current state of the headless using XML, it's gathering too much legacy code and starts to diverge from the GAMA core. Therefore I'd be more in favor of adding a new flag (eg. |
So without passing through all the legacy code, right ? A bit different but that makes me think that we could add functionalities to gama-server to generate the xml files and to run them too. |
@lesquoyb by using autosave of output (obviously no 3D i think) or save statement of snapshot.... we tested with Alexis in some previous coding camp but i did not remember exactly what it was, but it's possible |
While inspecting the code I noticed there's actually already a It is weird I never saw it mentioned anywhere and that even you @RoiArthurB was not aware of it. Currently its use is incompatible with the current parameters' verification, but I'm fixing this in the pr #362 along with few minor other things. It would still need to be documented though |
The pr restoring the |
Is your request related to a problem? Please describe.
From what I understand, currently with batch legacy if we need to run an experiment we have to run gama two times: once to generate an xml and a second time to run the experiment plan described in the xml.
We could probably add the possibility to create the xml and execute it right away with the same command, that would make things easier in many cases.
Describe the improvement you'd like
Be able to create and execute an experiment plan in the same command call for batch legacy
The text was updated successfully, but these errors were encountered: