Hi Ashley,
That's a good question, and probably more nuanced/complex than is covered in our documentation.
Right now the HET's observations are dominated by the HETDEX survey which uses Priority 0 time to observe its survey fields during dark time. If you want to observe at the same time as HETDEX, your program must have Priority 0 time in order to "interrupt" HETDEX. To calculate whether or not a given target collides with HETDEX on a given night, you can use this tool:
If your target does not conflict with HETDEX, then I would say that Priority 1 is usually adequate to get observations on timescales of days (weather-permitting, of course). We have had some other supernova programs in the observing queue and they make use of the
SYNDATE keyword which lets them specify the nights on which an observation would be useful. That helps us as we observe from the queue -- if we see a Priority 1 target that is observable only for a few nights, it will usually be the target of choice.
I know it's probably hard to know in advance whether a supernova will go off in a galaxy which is conflicted with HETDEX or not, but I hope that helps give you some perspective anyway. You might use that argument to justify asking for some P0 but mostly P1 time -- use the P0 time to observe really important time-sensitive targets which are in competition with HETDEX, and use the P1 time to observe those which are not conflicted.
Happy to help more if you have other questions about strategy, target submissions, etc!
Steven