-
Notifications
You must be signed in to change notification settings - Fork 12
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
Fix bug in handling starttime and endtime #486
Conversation
Previous version was failing to set starttime and endtime on saves. Also data loaded and cut had incorrect starttime and endtimes saved because they werne't being replaced.
Format Python code with psf/black push
I am not sure what to do with the error. The test that failed basically set |
Maybe those keys should be added in |
Three attributes in wf documents are special and need to be handled with care. They are: starttime, endtime, and npts. The reason they are so special in MsPASS is that all three must be closely linked with three internal attributes that are part of the C++ class (attributes of the class): npts, dt, and t0. The endtime attribute is more of a sanity check as endtime is a method of These cannot be handled in md2doc. The reason is that the "md" in md2doc is for Metadata. The starttime attribute in Metadata can become disconnected with the value of the "t0" attribute in a TimeSeries or Seismogram. I think a problem can happen because one can set t0 with a constuct like |
Codecov ReportAttention:
Additional details and impacted files@@ Coverage Diff @@
## master #486 +/- ##
=======================================
Coverage 53.58% 53.59%
=======================================
Files 144 144
Lines 22361 22365 +4
=======================================
+ Hits 11983 11987 +4
Misses 10378 10378 ☔ View full report in Codecov by Sentry. |
This is fixing #485 #484