Simon raised this in an email last week but it was buried near the bottom and has not yet been addressed:
"On the DDWG website there appear to be a large list of data files with known problems that have not been looked at in over a year. If these issues aren't going to be resolved we should delete the files. A temporary solution might be to embargo these files until they can be fixed. Either way I don't think we want them to be included in any analysis."
I've read through the list of "known data problem" files on that page and it sounds like they should be (at a minimum) removed from the normal mirror directory structure, if not entirely blacklisted. For example, the 20141008.1201.00.tig.rawacf file that was damaged in transport from the radar site and is completely unrecoverable - why should that still be distributed via the mirrors?
mts299
commented
4 years ago
Proposed File(s)
20141008.1201.00.tig.rawacf
Affiliated Mirror
Reason
Hi all,
Simon raised this in an email last week but it was buried near the bottom and has not yet been addressed:
"On the DDWG website there appear to be a large list of data files with known problems that have not been looked at in over a year. If these issues aren't going to be resolved we should delete the files. A temporary solution might be to embargo these files until they can be fixed. Either way I don't think we want them to be included in any analysis."
I've read through the list of "known data problem" files on that page and it sounds like they should be (at a minimum) removed from the normal mirror directory structure, if not entirely blacklisted. For example, the 20141008.1201.00.tig.rawacf file that was damaged in transport from the radar site and is completely unrecoverable - why should that still be distributed via the mirrors?
Cheers, Evan
Tasks