We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
The START keyword in runspec section seem to have a 2 small issues related to decimal seconds
This works fine
START 01 'NOV' 2018 12:00:30 /
when extracting simulation times (at report steps only) there is perfect agreement with Eclipse simulator
but this doesn't work.
START 01 'NOV' 2018 12:00:30.5 /
From what I can see, the last decimal in seconds is ignored by Flow.
With reference to second example above (01 'NOV' 2018 12:00:30.5)
Flow only output day month and year to STARTDAT keyword in SMSPEC (only 3 values in array).
'STARTDAT' 3 'INTE' 1 11 2018
Eclipse output 6 integer values
'STARTDAT' 6 'INTE' 1 11 2018 12 0 30500000
Notice that 6th integer value should be micro seconds.
Hopefully, It should not be much work to fix this.
The text was updated successfully, but these errors were encountered:
The second item has been fixed in libecl: equinor/resdata#642 - the first item is a bigger task to fix.
Sorry, something went wrong.
No branches or pull requests
The START keyword in runspec section seem to have a 2 small issues related to decimal seconds
1) Simulation time vector
This works fine
START
01 'NOV' 2018 12:00:30 /
when extracting simulation times (at report steps only) there is perfect agreement with Eclipse simulator
but this doesn't work.
START
01 'NOV' 2018 12:00:30.5 /
From what I can see, the last decimal in seconds is ignored by Flow.
2) Output to STARTDAT vector in summary file SMSPEC
With reference to second example above (01 'NOV' 2018 12:00:30.5)
Flow only output day month and year to STARTDAT keyword in SMSPEC (only 3 values in array).
Eclipse output 6 integer values
Notice that 6th integer value should be micro seconds.
Hopefully, It should not be much work to fix this.
The text was updated successfully, but these errors were encountered: