You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Right now we allow specifying sample_name with a derived attribute,
but then you have to specify the actual derivation within a subsample table, because the only want to link the sample table to the subsample table is via sample_name.
If instead there was a way to specify int he project config what was the attribute recipe used to construct the sample name... then you could link the two without having to specify the sample name in the subsample table.
use case: the refgenie build tools where I don't specify sample name in the main assets.csv file (the sample table), but I have to in the recipe_inputs.csv file (the subsample table) because that's the only way to link the two.
The text was updated successfully, but these errors were encountered:
Right now we allow specifying sample_name with a derived attribute,
but then you have to specify the actual derivation within a subsample table, because the only want to link the sample table to the subsample table is via sample_name.
If instead there was a way to specify int he project config what was the attribute recipe used to construct the sample name... then you could link the two without having to specify the sample name in the subsample table.
use case: the refgenie build tools where I don't specify sample name in the main assets.csv file (the sample table), but I have to in the recipe_inputs.csv file (the subsample table) because that's the only way to link the two.
The text was updated successfully, but these errors were encountered: