DF/data4es/017: steps (refined history). #380
Merged
Conversation
This file contains hidden or 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
We have `ctag` field with the current (last) AMI tag; but fully understand the process, to which the given task belongs, we can only by the whole chain of AMI tags (as they basically define the steps of data processing). This field is not required now for any use-case, but will allow more accurate classification of tasks by steps and, consequently, let us provide more adequate results in some use-cases.
New fields are added on stage 017 (adjustMetadata): * ctag_format_step; * ami_tags_format_step. There are different ways to say one step from another: * MC production step name (already exists as 'step_name' field); * current AMI tag + output data format; * chain of AMI tags + output data format. The latter is supposed to be the most universal, but initially only the first one was used, then for some cases the second was invented, and... ...and there's no good way to make things as they are supposed to be all at once. So we need all the possible namings. --- NOTE. Step names are based on the output data formats. They can be taken from task's metadata `output_formats` field, but it wasn't used before (when we needed tasks classification by format-based-steps). However, according to M.Borodin, field 'output_formats' and list of data formats, derived from the list of dataset names, must be exactly the same (if format is specified in 'output_formats', the task _will_ produce a dataset in the given format).
No one will be interested in statictics related to these formats. In theory. --- NOTE I'd say that "technical" formats are "LOG" and "TXT", but (according to M.Borodin) TXT is a proper data format.
This was referenced Jul 29, 2020
Evildoor
approved these changes
Jul 29, 2020
4 tasks
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.
New fields are added on stage 017 (adjustMetadata):
(Partially) overrides #371.