@flowerthrower @mnfarooqi @kayaercument @ctminh Let me annoy you again with this idea. I think we should consider adding queue management routines to the QDMI specification. I think this would simplify submission and handling priorities.
-
QDMI_control_submit and QDMI_control_cancel would stay the same. We would have to simply add a priority field to the QDMI_Fragment
-
We would simply have to add 1) QDMI_query_queue_property_f to get the total execution time for all the jobs in the queue of a device. And 2) QDMI_query_queue_priorities to get an array with all the priorities (maybe this can be done also with something similar to QDMI_query_queue_property_XXX). The execution time of a circuit would be attached to the QDMI_Fragment by either the pass runner or the submitter (just adding up execution time for each gate along the critical path right before submitting). We could ask for the execution time of each gate along the CP with, for example, QDMI_query_gate_property_f
@flowerthrower @mnfarooqi @kayaercument @ctminh Let me annoy you again with this idea. I think we should consider adding queue management routines to the QDMI specification. I think this would simplify submission and handling priorities.
QDMI_control_submitandQDMI_control_cancelwould stay the same. We would have to simply add a priority field to theQDMI_FragmentWe would simply have to add 1)
QDMI_query_queue_property_fto get the total execution time for all the jobs in the queue of a device. And 2)QDMI_query_queue_prioritiesto get an array with all the priorities (maybe this can be done also with something similar toQDMI_query_queue_property_XXX). The execution time of a circuit would be attached to theQDMI_Fragmentby either the pass runner or the submitter (just adding up execution time for each gate along the critical path right before submitting). We could ask for the execution time of each gate along the CP with, for example,QDMI_query_gate_property_f