-
Notifications
You must be signed in to change notification settings - Fork 3
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
UWS: Retrieve the .sav file #38
Comments
Do you mean a precompiled IDL sav file ? |
We already have the possibility with ExPRES (with an option in the json input file) to produce a sav file. |
OK, it should be easy then. |
It's done for the job ExPRES-dev. |
I'm sorry, I realise that I must not have been clear in my request. |
Yes that is what I have understood. In your latest runs, you can fetch a file 'SERPE.sav'. I think that this one is produced by the command '@serpe_compile'. I just removed this file from the outputs. Do you know where your .sav is meant to be saved ? In the same directory as the cdf file ? |
for the MIME-type, |
I forgot about this SERPE.sav file. It's also useful to have this file as an output, yes!
Yes, in the same directory as the cdf file. |
I just tried to run a simulation with the correct entry to ask ExPRES to produce the sav file (containing the same infos than the CDF), and it worked. Thanks @aicardi-obspm. @BaptisteCecconi : Do we want to also give the SERPE.sav (produced by the "@serpe_compile" command) file as an output? |
I didn't understand where the sav file was created in your jobs from yesterday. They were just not created! I wait for Baptiste's answer for the SERPE.sav file before closing the issue. |
@BaptisteCecconi, can you give us your thought on having or not the SERPE.sav file as an output? This file contains all the procedures and functions used for the simulation. |
For the ExPRES-dev job, yes, that would be good too. |
UWS : add the possibility to retrieve a .sav file.
The text was updated successfully, but these errors were encountered: