Fetch read length info for run instead of just lane 1 #66
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.
Description:
Previously, get_metadata.py reported the read and index length based on the information from lane 1 which could be misleading in some cases. Therefore, it was decided that the script should be updated so that it shows the read length setting for the run instead.
In this update, this is achieved by fetching length information from RunInfo.xml
Also updated actions/cache from v2 --> v4.2.2 to enable automatic testing
Risk analysis:
The scripts will most likely fail if there are updates to the structure of the RunInfo.xml file. However, the damage from this would be minimal and should be noticed immediately.
Validation procedure:
Run ngi work flow, generate reports and makes sure that the expected read and index lengths are printed in the report.