Skip to content
This repository has been archived by the owner on Jun 21, 2023. It is now read-only.

V22 CI updates for consensus_seg_with_status.tsv (2/N release) #1449

Merged
merged 19 commits into from
Jun 7, 2022

Conversation

jharenza
Copy link
Collaborator

@jharenza jharenza commented Jun 1, 2022

Purpose/implementation Section

What scientific question is your analysis addressing?

Add consensus_seg_with_status.tsv to subsetting

What was your approach?

What GitHub issue does your pull request address?

#1426

Directions for reviewers. Tell potential reviewers what kind of feedback you are soliciting.

Which areas should receive a particularly close look?

Is there anything that you want to discuss further?

Is the analysis in a mature enough form that the resulting figure(s) and/or table(s) are ready for review?

Results

What types of results are included (e.g., table, figure)?

What is your summary of the results?

Reproducibility Checklist

  • The dependencies required to run the code in this pull request have been added to the project Dockerfile.
  • This analysis has been added to continuous integration.

Documentation Checklist

  • This analysis module has a README and it is up to date.
  • This analysis is recorded in the table in analyses/README.md and the entry is up to date.
  • The analytical code is documented and contains comments.

@jharenza jharenza changed the base branch from master to v22-release June 1, 2022 19:04
jaclyn-taroni and others added 4 commits June 1, 2022 21:16
* WIP: update shell

* Revert RUN_LOCAL change

* Fix missing curly bracket

* Account for TMB files

Don't skip header!

* Add mkdir to cover case when subsetting is skipped first
@jharenza jharenza changed the title V22 CI updates for consensus_seg_with_status.tsv V22 CI updates for consensus_seg_with_status.tsv (2/N release) Jun 2, 2022
@jharenza
Copy link
Collaborator Author

jharenza commented Jun 3, 2022

@jaclyn-taroni and @migbro, we are in business!

@jharenza jharenza requested a review from jaclyn-taroni June 3, 2022 01:37
@migbro
Copy link
Contributor

migbro commented Jun 3, 2022

@jharenza Great to hear! I will kill that ec2 instance then

Base automatically changed from v22-release to master June 7, 2022 16:56
Copy link
Member

@jaclyn-taroni jaclyn-taroni left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍🏻 I did make some of these changes and therefore am not a totally independent reviewer, but here we are!

@@ -31,6 +31,10 @@ cd "$script_directory" || exit
# generated via these scripts
FULL_DIRECTORY=../../data/$RELEASE
SUBSET_DIRECTORY=../../data/testing/$RELEASE
# If run subsetting only, we need to make this directory
if [ ! -d ${SUBSET_DIRECTORY} ]; then
mkdir -p ${SUBSET_DIRECTORY}
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It doesn't matter, but I don't think you need this logic if you use -p with mkdir.

@jaclyn-taroni
Copy link
Member

This module is upstream of CI and doesn't get tested. Merging without it!

@jaclyn-taroni jaclyn-taroni merged commit ef2b1e3 into master Jun 7, 2022
@jaclyn-taroni jaclyn-taroni deleted the v22-ci-local branch June 7, 2022 17:01
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants