-
Notifications
You must be signed in to change notification settings - Fork 2
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
New yeoda filename #21
Conversation
…nd set the date format within this methods. The relative orbit is written into the extra_field which accepts more general inputs. Adapted the decoding and encoding methods according to this new field definition.
…he new Yeoda filenaming.
…een date and datetime using the isinstance function in the right order. Adapted the encoding method of the datetime field by checking for the 'T' to get time information. Removed deconding and encoding methods for time.
…ion a length of zero.
… statement to catch the corresponding inputs.
…s a variable length field at the end of it. Implemented rule which requires a delimiter in case of a variable length field.
… length to the __init__ function of the SmartFilenamePart.
…s to match Yeoda naming class.
… errors in case of an empty field.
…into new_YeodaFilename
…hfinder into new_YeodaFilename
…in case of smaller arguments compared to the defined length. Additionally, all empty fields are represented by a single pad. Adapted SmartFilenamePart class to handle this functionality.
…d if the argument is smaller then the expected length.
…compact option is True. Added if statement in the __set_item__ method to get this functionality.
…hfinder into new_YeodaFilename
…limiter within a field with variable length.
…limiter within a field with variable length when reading filename.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks fine for me.
a) yeoda-filename works as expected
b) all tests on my local Windows machine are green
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- works fine with S1 Sigma
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks very good! Three changes still need to be done:
conda_env.yml
Outdated
@@ -2,9 +2,9 @@ name: geopathfinder | |||
channels: | |||
- defaults | |||
dependencies: | |||
- python=3.6 | |||
- python |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would prefer to restrict the Python version to e.g. python=3.7
. Simply using python
is too general.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
actually, can we remove python at all?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
it should work for python 3. for all python 3 versions (3.6, 3.7,..)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would recommend >= 3.6
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The issue I see at the moment is that we use the same conda yml file for Travis. I prefer to have separate yml files for testing each Python version with Travis. This ensures that each Python version works/is supported and is always tested and makes it easier to reset package dependencies for a specific Python version. In the main yml file I agree with @sebhahn , there we could set python >= 3.6
.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
is already set to python >= 3.6 now
please proceed and implement the steps you suggested - i want to release a new version...
…od of SmartFilenamePart to allow a more performant field concatenation;
… all existing file naming conventions.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great, all changes are fine from my side!
Implementation of the new filename and folder logic with a more compact and general purpose use. The corresponding changes include: