Closed alejoe91 closed 8 months ago
Since all jobs parameters are stored in the database, I believe we can generalize this with two functionalities:
{
input: {… input files and configuration …}
resources: {… resources configuration …}
processor: {… processor parameters …}
}
@luiztauffer @alejoe91
I implemented this somewhat differently that proposed (for now).
But the upshot is... there are now a "save parameters" and "load parameters" buttons at the top of the parameter input form.
It saves the parameters in the "parameter-sets" folder of the project.
@magland this looks great, thanks! I just tried it, would it be possible to load the parameters from a json file? It could be the one we can export from the Job panel for example. In this way people can easily share and re-use their job configurations in different Projects
@luiztauffer This should be working now. See #121.
A user might want to save a preset of parameters for a specificic app.
These could be saved in the project folder and rendered as a dropdown if available