Open alanbchristie opened 1 year ago
One thing that is observed in the stack backend log is this: -
2023-07-05T13:41:57+0000 create():2997 INFO # + DownloadStructures.post
2023-07-05T13:41:57+0000 create():2998 INFO # request.data={"target_name": "NCS1", "proteins": "", "event_info": false, "sigmaa_info": true, "diff_info": true, "trans_matrix_info": false, "NAN": false, "mtz_info": false, "cif_info": false, "NAN2": false, "map_info": false, "single_sdf_file": true, "sdf_info": false, "pdb_info": false, "bound_info": true, "metadata_info": true, "smiles_info": true, "static_link": false, "file_url": ""}
2023-07-05T13:41:57+0000 create():3051 INFO # Given target_name "NCS1"
2023-07-05T13:41:57+0000 create():3072 INFO # No proteins supplied
2023-07-05T13:41:57+0000 create():3087 INFO # Collected 0 proteins <QuerySet []>
And this occurs after an attempt to collect Proteins for the given Target ID with: -
proteins = Protein.objects.filter(target_id=target.id).values()
So I suspect that the above query is simply not returning any Protein records.
It might be worth enhancing the log so that the Target ID can be seen. Here we can assume is is the ID for
NCS1
When I lookup NCS1
on the staging stack I get target.id=87
and 129 results when I run Protein.objects.filter(target_id=87).values()
Pretty sure this is actually part of #1075. @tdudgeon and @kaliif to confirm.
If I'm right, please move to "Invalid/duplicate" swimlane.
This is wontfix after all.
Warren reports that crystallographic data is missing from target downloads. He spotted this in his experiment today (NCS1) at about 14:11. Warren reports that eatery files are missing or the Download fails: -