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
Scottx611x/fix same name analysis results #2099
Scottx611x/fix same name analysis results #2099
Conversation
…ess if there is > 1 corresponding AnalysisResults
…alysis.attach_outputs_dataset()`
…on output, but this isn't necessarily a failure state
…'s nodes after they've been populated.
Codecov Report
@@ Coverage Diff @@
## develop #2099 +/- ##
===========================================
+ Coverage 45.47% 47.13% +1.65%
===========================================
Files 411 411
Lines 27799 28583 +784
Branches 1313 1313
===========================================
+ Hits 12642 13472 +830
+ Misses 15157 15111 -46
Continue to review full report at Codecov.
|
…()` by constraining query to Nodes used as input for a given analysis run.
…lysisNodeConnection in the case where there are many results w/ the same name. Needs tests
…n have the same name
…ence the same methods.
…rt against more readable
refinery/core/models.py
Outdated
# attribute to the derived data file node to indicate | ||
# which output of the tool it corresponds to | ||
# connect outputs that are not inputs for any data transformation | ||
# attribute to the derived data file node to |
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.
fix comment line
default dict usage, tuples for mapping |
… AnalysisResult mapping as its more clear than a dict
When a DataSetCollection is used as input to a workflow which only accepts a
data_input
, said workflow will be run (N x the number of elements in the collection) with the potential to create N derived data nodes with the same name if the workflow doesn't have a dynamically namedlabel
for it'soutputs
.Analysis.attach_outputs_dataset()
had logic in place to not attach derived data nodes to their AnalysisNodeConnections if this scenario occured, but this is behavior that we would like now.Reviewed side by side w/ @mccalluc