Open teague-23andme opened 1 week ago
Hi @teague-23andme,
Thank you for using gwas-sumstats-tools and for reporting the issue you encountered.
gwas-sumstat-tools is designed to format GWAS summary statistic data not originally in the GWAS-SSF format into the correct format and to validate that an input file meets the GWAS-SSF standards before submission to the GWAS Catalog.
The metadata generation function currently has a primary focus on internal use. It retrieves metadata via our REST API or internal ingest API via GCST ID and creates the YAML file. GCST number is essential for this purpose.
I noticed you're using version v1.0.5, one of our earlier releases, and I hope the combination of the gwas-ssf format
and --generate-metadata
options wasn’t confusing.
Could you share more about your specific use case? This will help us understand if the latest release of gwas-sumstats-tools could better support your needs.
System information
Description of the Issue
The
format
command with--generate-metadata
crashes for a filename that doesn't containGCST
, even if the metadata is otherwise valid due to attempting to concatenate a string andNone
.Creating a symlink to the file with a GCST name processes the metadata (more or less) as expected, except that it adds the GWAS Catalog IDs.
Calling the
format
command with aGCST
filename that doesn't exist, still processes and writes the metadata file.Ideally,
gwas_id
andgwas_catalog_api
shouldn't be forced to be inferred for files they are not required of.Error Message
First 10 Rows of the Input File
empty.tsv
:minimal.yaml
: