Hi, I started my DESeq2 jobs on Friday afternoon and they are still churning. Is that normal? Should I stop them and start again? I initially received an error "Required metadata values are missing. Some of these values may not be editable by user. Selecting "auto-detect" will attempt to fix these values. I did that and I get the message "Metadata is being autodetected" when I click on the eye icon. thanks, Karl
There may have been a problem during job execution leading to a metadata conflict. This is usually a transitory server side issue.
I see the auto-detect for metadata running on several datasets. After two hours, these should have completed.
Permanently deleting those results/datasets and rerunning DeSeq2 is probably the best way forward. If the jobs end in an odd state again (metadata problems or other), please write back leaving those datasets intact (not deleted, not auto-detected) and we can follow up on what the problem may be. The inputs look OK from a quick review.
Thanks! Jen, Galaxy team