Issue when using _time_utc as df index in parallel runs
#5
Assignees
Comments
elcorto
added a commit
that referenced
this issue
May 25, 2022
See #4 and #5 Multiuple _pset_ids can end up having the same index if parallel runs start at the same time and index == _time_utc which is the start time before func() is called. Use integer index now. Use time for verbose printing though. Also replace deprecated df.append() by pd.concat(). Add new _pset_runtime field where we record the run time of calling func().
Closed
elcorto
added a commit
that referenced
this issue
May 25, 2022
Multiuple _pset_ids can end up having the same index if parallel runs start at the same time and index == _time_utc which is the start time before func() is called. Use integer index now. Use time for verbose printing though. Also replace deprecated df.append() by pd.concat(). Add new _pset_runtime field where we record the run time of calling func(). Closes #4 and #5
|
Fixed by 4888703 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Multiuple
_pset_ids can end up having the same index if runs start at the same time.The text was updated successfully, but these errors were encountered: