Search results

Issue with Bridges 2

Status: Open.

#21 In hubmapconsortium/py-hubmap-dbgap;

· icaoberg opened on Aug 7, 2024

Compress results

Status: Open.

#15 In hubmapconsortium/py-hubmap-dbgap;

· icaoberg opened on Feb 15, 2024

Issue with UFlorida

Status: Open.

#14 In hubmapconsortium/py-hubmap-dbgap;

· icaoberg opened on Feb 15, 2024

Upload Jupyter Notebooks

documentationImprovements or additions to documentationImprovements or additions to documentation

enhancementNew feature or requestNew feature or request

Status: Open.

#12 In hubmapconsortium/py-hubmap-dbgap;

· icaoberg opened on Aug 11, 2023

Deploy Aspera Connect in Singularity

documentationImprovements or additions to documentationImprovements or additions to documentation

Status: Open.

#11 In hubmapconsortium/py-hubmap-dbgap;

· icaoberg opened on Aug 11, 2023

I renew my [previous comment](https://github.com/hubmapconsortium/py-hubmap-dbgap/pull/4#discussion_r1187602356) about the potential for KeyErrors using this pattern, either occurring in the traversal of metadata or when extracting the value from the {"Illumina": "ILLUMINA"} dict.

Status: Open.

#7 In hubmapconsortium/py-hubmap-dbgap;

· icaoberg opened on May 11, 2023

Additionally/alternatively, breaking out the this part where you parse the JSON entirely might be desirable. E.g. you could instead deserialize the JSON into a dataclass ([example](https://stackoverflow.com/a/76103446)) which you instantiate and refer to in the submission function. That should break things up, add some clarity, and help more safely retrieve values from the JSON.

Status: Open.

#6 In hubmapconsortium/py-hubmap-dbgap;

· icaoberg opened on May 11, 2023