Added functionality to save to a relative file path. #13
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
…ted and verified on Ubuntu 18.04.
…ders. Documentation for this functionality is sparse, but it is not a complex function.
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.
Issue: Saving to 1 input and 1 output clutters the folder environment
Proposed solution: With 1 campaign name, save input and outputs like so
input output
| |
| |
campaign name campaign name
Note: I'm not sure if this is most efficient. Maybe making the "campaign name" the parent folder instead of child folder would be easier. Following the Bernese campaign file hierarchy? In that case changes are only repositioning the directory names in gpsxtr.py, leorun.py, leogui.py, pubplt.py and rnpath.py