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

UWS: Retrieve the .sav file #38

Open
CorentinLouis opened this issue Nov 26, 2020 · 12 comments
Open

UWS: Retrieve the .sav file #38

CorentinLouis opened this issue Nov 26, 2020 · 12 comments
Assignees

Comments

@CorentinLouis
Copy link
Collaborator

UWS : add the possibility to retrieve a .sav file.

@aicardi-obspm
Copy link
Collaborator

Do you mean a precompiled IDL sav file ?
It's possible but will it work without tweaking some paths ?

@CorentinLouis
Copy link
Collaborator Author

We already have the possibility with ExPRES (with an option in the json input file) to produce a sav file.
The idea will be to retrieve this .sav file in the UVW outputs

@aicardi-obspm
Copy link
Collaborator

OK, it should be easy then.
Do you expect a specific mime-type for the sav file ? I will use application/octet-stream by default.

@aicardi-obspm
Copy link
Collaborator

It's done for the job ExPRES-dev.

@CorentinLouis
Copy link
Collaborator Author

I'm sorry, I realise that I must not have been clear in my request.
In ExPRES simulations, you can produce an output .sav file that contains similar information to what is in the cdf. We would like to be able to add to UWS the ability to retrieve this .sav file.

@aicardi-obspm
Copy link
Collaborator

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 ?

@BaptisteCecconi
Copy link
Collaborator

for the MIME-type, application/octet-stream is fine.

@CorentinLouis
Copy link
Collaborator Author

CorentinLouis commented Jun 11, 2021

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.

I forgot about this SERPE.sav file. It's also useful to have this file as an output, yes!

Do you know where your .sav is meant to be saved ? In the same directory as the cdf file ?

Yes, in the same directory as the cdf file.

@CorentinLouis
Copy link
Collaborator Author

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?

@aicardi-obspm
Copy link
Collaborator

I didn't understand where the sav file was created in your jobs from yesterday. They were just not created!
I'm happy if the current setting suits you.

I wait for Baptiste's answer for the SERPE.sav file before closing the issue.

@CorentinLouis
Copy link
Collaborator Author

@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.

@BaptisteCecconi
Copy link
Collaborator

For the ExPRES-dev job, yes, that would be good too.

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