-
Notifications
You must be signed in to change notification settings - Fork 27
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
Interactive usage of csv_export2 #308
Comments
This will move the export further away from the current direction of ERT development and no shared disk for data communication. I'm suggesting that this command line tool is instead implemented closer to the |
Fair point, an endpoint for this has always been relevant to make for
|
Could you please elaborate on why the situation arise when you do not have a runpath file? |
This functionality is not intended to be used in ERT-config, so it is not documented as such. |
Those are good user stories that I understand that you are motivated to cater for! Still, |
User story 1 is to aid debuggers for problems related to Lets ignore user story 3 for now. And add that we don't want to duplicate this code anywhere. ERT setups is the core target for I am left with dropping this dead, or merging into |
My main concern here is that we are building upon the export capability where the user will have to work explicitly on the runpath(file), instead of exporting a case. This is in my opinion an anti-pattern that is orthogonal to the introduction of a data API and starting to depend less on the shared disks; which are key to the upcoming FMU efforts. My hope earlier was that we could actually start backing If we agree that Any thoughts on this @lars-petter-hauge or @oyvindeide? |
Think at this point we can close this issue, we are hopefully close to implementing a csv_export in |
Allow interactive usage of csv_export2 outside ERT
For interactive usage outside of ERT, a command line API to
csv_export2
can be a good ideaDescribe the solution you'd like
csv_export2 already has a command line API, but it requires an existing RUNPATHFILE which is non-trivial to create ad-hoc. Suggest to allow a glob-path to be supplied instead of RUNPATHFILE, so that if csv_export2 encounters a non-existing runpath file, it will attempt to interpret it as a glob-path that can be supplied to
EnsembleSet
s initialization code as afrompath
argument.The text was updated successfully, but these errors were encountered: