-
Notifications
You must be signed in to change notification settings - Fork 94
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
smspec_node is_historical has false positives #708
Comments
Is this still relevant? Looks a lot like #707 . It'd be nice to have documentation of how to detect historical data. |
It is somewhat related to, but not addressed in #707 @dotfloat |
Cool. Does ECLIPSE have any documentation of what constitutes historical data? Or is this a naming convention and we just have to guess? |
I haven't seen a clear definition, on the other hand: I must admit I haven't read the whole thing 😬🙈 But as I mention above, as far as I know, only field, group and well vectors can be historical (potentially also completions, but I don't think so). And the keyword part will always end on an H like the current implementation (afaik). So my suggestion is to reduce risk of false positives by only checking the types above. My suggested (maybe not completely a) solution should of course be easy to implement. |
Poking @markusdregi , @eivindsm , et al. |
Currently only checks if vector ends with
H
.Several examples of vectors which return
true
, but should returnfalse
, exist,. e.g.:MONTH
andTCPUH
.History is defined through keywords
WCONHIST
andWCONINJH
, hence vectors that are not ofecl_smspec_var_type
:ECL_SMSPEC_WELL_VAR
,ECL_SMSPEC_GROUP_VAR
orECL_SMSPEC_FIELD_VAR
should not be possible as far as I know.Checking vector
ecl_smspec_var_type
should therefore reduce the risk of false positives.The text was updated successfully, but these errors were encountered: