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
When I run a batch in Chowda and download the MMIF, sometimes the same MMIF file is included twice in the zip archive.
The expected output is one MMIF file per guid in the batch.
Reproduction steps
Look at the ten consecutive batches between Batch 38 and Batch 47. They are intended to be identical except for the batch name.
(I was running 10 identical batches to investigate a question about indeterminacy and degree of variation in CV model classifications.)
Across those 10 batches there was some differences in the output MMIF. That's fine, and due to the nature of the SWT app. The weird issue is that, for two batches, when I downloaded the MMIF, the same MMIF file was included twice in the zip archive. Those were batch 42 and batch 46.
Expected behavior
It should provide only one MMIF file per guid.
Screenshots
No response
Browsers
No response
OS
No response
Additional context
No response
The text was updated successfully, but these errors were encountered:
Description
When I run a batch in Chowda and download the MMIF, sometimes the same MMIF file is included twice in the zip archive.
The expected output is one MMIF file per guid in the batch.
Reproduction steps
Look at the ten consecutive batches between Batch 38 and Batch 47. They are intended to be identical except for the batch name.
(I was running 10 identical batches to investigate a question about indeterminacy and degree of variation in CV model classifications.)
Across those 10 batches there was some differences in the output MMIF. That's fine, and due to the nature of the SWT app. The weird issue is that, for two batches, when I downloaded the MMIF, the same MMIF file was included twice in the zip archive. Those were batch 42 and batch 46.
Expected behavior
It should provide only one MMIF file per guid.
Screenshots
No response
Browsers
No response
OS
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: