o `۷im@sddlmZmZmZddlmZddlmZddlm Z ddl m Z m Z er,ddl mZe GdddZe Gd d d eZd S) ) TYPE_CHECKINGDictOptional tag_scheduler)Trial)DEFAULT_METRIC) DeveloperAPI PublicAPI)TuneControllerc@s eZdZdZdZdZdZdZdZdZ dd Z e d d Z e d d Z deedeedefddZdddefddZdddefddZdddededefddZdddedefddZdddefdd Zdddeefd!d"Zdefd#d$Zd%efd&d'Zd%efd(d)ZdS)*TrialSchedulerzInterface for implementing a Trial Scheduler class. Note to Tune developers: If a new scheduler is added, please update `air/_internal/usage.py`. CONTINUEPAUSESTOPNOOPNTcCs t|dSNrselfrY/home/ubuntu/vllm_env/lib/python3.10/site-packages/ray/tune/schedulers/trial_scheduler.py__init__!s zTrialScheduler.__init__cC|jSr)_metricrrrrmetric$zTrialScheduler.metriccCrr)_supports_buffered_resultsrrrrsupports_buffered_results(rz(TrialScheduler.supports_buffered_resultsrmodereturncKs,|jr|rdS|r ||_|jdurt|_dS)aPass search properties to scheduler. This method acts as an alternative to instantiating schedulers that react to metrics with their own `metric` and `mode` parameters. Args: metric: Metric to optimize mode: One of ["min", "max"]. Direction to optimize. **spec: Any kwargs for forward compatibility. Info like Experiment.PUBLIC_KEYS is provided through here. FNT)rr)rrrspecrrrset_search_properties,s  z$TrialScheduler.set_search_propertiestune_controllerr trialcCt)z5Called when a new trial is added to the trial runner.NotImplementedErrorrr!r"rrr on_trial_addEzTrialScheduler.on_trial_addcCr#)znNotification for the error of trial. This will only be called when the trial is in the RUNNING state.r$r&rrron_trial_errorJszTrialScheduler.on_trial_errorresultcCr#)zCalled on each intermediate result returned by a trial. At this point, the trial scheduler can make a decision by returning one of CONTINUE, PAUSE, and STOP. This will only be called when the trial is in the RUNNING state.r$rr!r"r*rrron_trial_resultQs zTrialScheduler.on_trial_resultcCr#)zNotification for the completion of trial. This will only be called when the trial is in the RUNNING state and either completes naturally or by manual termination.r$r+rrron_trial_complete\z TrialScheduler.on_trial_completecCr#)zCalled to remove trial. This is called when the trial is in PAUSED or PENDING state. Otherwise, call `on_trial_complete`.r$r&rrron_trial_removefszTrialScheduler.on_trial_removecCr#)zCalled to choose a new trial to run. This should return one of the trials in tune_controller that is in the PENDING or PAUSED state. This function must be idempotent. If no trial is ready, return None.r$)rr!rrrchoose_trial_to_runnr.z"TrialScheduler.choose_trial_to_runcCr#)z=Returns a human readable message for printing to the console.r$rrrr debug_stringxr(zTrialScheduler.debug_stringcheckpoint_pathcCr#)z$Save trial scheduler to a checkpointr$rr2rrrsave}zTrialScheduler.savecCr#)z(Restore trial scheduler from checkpoint.r$r3rrrrestorer5zTrialScheduler.restore)__name__ __module__ __qualname____doc__r rrrrrrpropertyrrrstrboolr rr'r)rr,r-r/r0r1r4r6rrrrr sV        r cseZdZdZfddZdddefddZdddefd d Zddded ed e fd dZ ddded efddZ dddefddZ ddd e efddZd e fddZZS) FIFOSchedulerz;Simple scheduler that just runs trials in submission order.cstdSr)superrr __class__rrrszFIFOScheduler.__init__r!r r"cCdSrrr&rrrr'zFIFOScheduler.on_trial_addcCrBrrr&rrrr)rCzFIFOScheduler.on_trial_errorr*rcCstjSr)r r r+rrrr,szFIFOScheduler.on_trial_resultcCrBrrr+rrrr-r(zFIFOScheduler.on_trial_completecCrBrrr&rrrr/rCzFIFOScheduler.on_trial_removecCsH|D] }|jtjkr|Sq|D] }|jtjkr!|SqdSr) get_trialsstatusrPENDINGPAUSEDr&rrrr0s    z!FIFOScheduler.choose_trial_to_runcCsdS)Nz Using FIFO scheduling algorithm.rrrrrr1rCzFIFOScheduler.debug_string)r7r8r9r:rrr'r)rr<r,r-r/rr0r1 __classcell__rrr@rr>s0    r>N)typingrrrray.air._internal.usagerray.tune.experimentrray.tune.resultrray.util.annotationsr r "ray.tune.execution.tune_controllerr r r>rrrrs    y