Datetime #1
Open
Datetime #1
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…lders, so they are statically set. Passed the value accordingly, to the corresponding routine.
…statically through a string
|
Seems like putting `date` in the commits expanded on to the actual date. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Use of the intrinsic
dateto name and search for the output directory names leads to a crash whenever date changes on the hardware clock.This issue was encountered during an HPC run. The code ran overnight, and crashed when it tried to probe the previous
datedirectory. To circumvent this issue, a string containing thedatetimeduring the start of the run is created. This static string a) names the output directory, b) does not change during the run. When the code probes for the previous results' directory, it will correctly find it regardless of the current date.