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
Hi all ! We are trying to run mocks for SV3 . By using fba_run for our mock catalogue, we get outputs like “fba-000012.fits” . We want to figure out the meaning of each column to understand these output files in detail so that we can use some methods to test the fiber-collision effects . We found https://desidatamodel.readthedocs.io/en/latest/DESI_TARGET/fiberassign/tile-TILEID-FIELDNUM.html#hdu5 this page describes the fba outputs ,but it seems outdated . For example , it just mentions ‘FIBERSTATUS’ as Fiber status mask; 0=good but we got some other numbers . Some other columns like ‘FA_TYPE’ and ‘FA_TARGET’ are Description needed …. Do you know if there are any documents describing these columns in detail or where we can find some files like Fiber status mask so that we can figure out which fiber couldn't work properly because of fiber collision ? Thank you so much 😊
The text was updated successfully, but these errors were encountered:
Hi all ! We are trying to run mocks for SV3 . By using fba_run for our mock catalogue, we get outputs like “fba-000012.fits” . We want to figure out the meaning of each column to understand these output files in detail so that we can use some methods to test the fiber-collision effects . We found https://desidatamodel.readthedocs.io/en/latest/DESI_TARGET/fiberassign/tile-TILEID-FIELDNUM.html#hdu5 this page describes the fba outputs ,but it seems outdated . For example , it just mentions ‘FIBERSTATUS’ as Fiber status mask; 0=good but we got some other numbers . Some other columns like ‘FA_TYPE’ and ‘FA_TARGET’ are Description needed …. Do you know if there are any documents describing these columns in detail or where we can find some files like Fiber status mask so that we can figure out which fiber couldn't work properly because of fiber collision ? Thank you so much 😊
The text was updated successfully, but these errors were encountered: