Open alxogm opened 4 years ago
Thanks for reporting this. Please track down whether these are edge pixels that just barely touch the footprint, or whether they are some other failure in the middle of the footprint. The footprint file changed in March 2020 (i.e. after the buzzard mocks) which slightly changed the edges. Options:
Hi,
I encountered the same problem when I am running the script. When I was trying to locate where the missing pixels are, I plotted the footprint output by desimodel. Yellow pixels are the ones with missing Buzzard files.
I am not sure this is the right DESI footprint, but it does look like the missing pixels lie on the edge of the footprint.
This problem also shows up in select_mock_targets, no surprise.
@zchvsre can I trouble you to reach out to @j-dr (maybe on the DESI slack?) and see if he would be able to build out the Buzzard footprint to match the latest/final DR9 footprint? Certainly I think the full-footprint Buzzard mocks will be very helpful going forward.
@moustakas Yeah sure!
@moustakas Hi! @j-dr is in the process of producing a large number of new mocks and he will update the footprint in those mocks!
@moustakas Hi! @j-dr is in the process of producing a large number of new mocks and he will update the footprint in those mocks!
@zchvsre @j-dr any updates on this ticket?
A full footprint run of mpi_run_select_mock_targets including contaminants failed for a few pixels, due to some Buzzard mock files missing, below is the full error message.
Same for (and maybe a few others I've not noticed):