Issue with Array Input

Post author
Seunghun Han

Hi,

A Terra method I'm using takes Array[File]+ input "gcnv_model_tars" in the screenshot,
and the method has been working without problem. 

However, when I used the same method this morning, the array file input is passed in a wrong way. For example, it looks like the input is interpreted as a list of a list now with additional [ ] added as shown below, and it is causing the workflow to fail

But the same workflow I ran on Nov 20 didn't have the issue and the array file is input as a list


Has there been change in the system as to how input array files are interpreted? 

 

Comments

3 comments

  • Comment author
    Seunghun Han

    Hi,

    I figured out that the list was set as a string, but not as a list attribute, so I clicked the "Attribute is a list" box, and I also had to manually 
    insert bucket paths for each file. I could get away with it since my array only had around 10 files, but it would be better if there is an easy 
    way to modify datamodel to have a list attribute 

    0
  • Comment author
    Jason Cerrato

    Hi Seunghun,

    Thanks for writing in. A member of our team will take a look at your original inquiry as soon as they can and get back to you.

    To comment on your follow-up post, the Terra team recently released a feature that allows you to upload TSVs with arrays directly to Terra, without having to do the manual work of defining the attribute list items in the UI. You can read more about that here: https://support.terra.bio/hc/en-us/community/posts/360054716892/comments/4409077727387

    Long term we definitely want to make sure that your WDL is designed as needed to write the array outputs back to the data model successfully, but if you needed you should be able to download your data table TSV, fix your array(s), and upload the new version back to the workspace.

    Kind regards,

    Jason

    0
  • Comment author
    Emil Furat
    • Edited

    Hi Seunghun,

     

    To follow up on your original inquiry: I talked with some members of our engineering team about the behavior you observed and they let me know that there has been no change in the way that array input files are interpreted.

     

    Do you happen to know whether this change occurred before or after running your workflow?

     

    Kind regards,

    Emil

    0

Please sign in to leave a comment.