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

START keyword (RUNSPEC input) and STARTDAT keyword (SMSPEC output) #915

Open
tskille opened this issue Aug 1, 2019 · 1 comment
Open

Comments

@tskille
Copy link
Contributor

tskille commented Aug 1, 2019

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

Date eclipse Flow Diff
2.11.2018 0.4996528 0.4996528 0.00E+00
1.12.2018 29.4996529 29.4996529 0.00E+00

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.

Date eclipse Flow Diff
2.11.2018 0.499647 0.4996528 -5.78E-06
1.12.2018 29.4996471 29.4996529 -5.72E-06

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

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

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

2 participants