code:ga_scheduling
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
code:ga_scheduling [2009/01/11 13:07] – How to add new objective pkubanek | code:ga_scheduling [2009/01/16 13:50] – pkubanek | ||
---|---|---|---|
Line 6: | Line 6: | ||
Important is to remember that lower constraint violation value means better schedule, and higher objective function value means better schedule. If you come to objective which naturally produces better schedules when lower value is calculated, you can easily change function by using //1/f(x)// instead. | Important is to remember that lower constraint violation value means better schedule, and higher objective function value means better schedule. If you come to objective which naturally produces better schedules when lower value is calculated, you can easily change function by using //1/f(x)// instead. | ||
+ | |||
+ | In order to use GA scheduling, you will need to fill in database. You will also find it useful to use //pyrts2// to visualise schedule, so you will be able to see how scheduling algorithm behaves. | ||
+ | |||
+ | ===== Database setup ===== | ||
+ | |||
+ | //Note: Currently you need to build database from REL_0_8_0 branch. See bellow how to retrieve it.// | ||
+ | |||
+ | You need to fill **tickets** and **accounts** tables. | ||
+ | |||
+ | ^ Field name ^ Description ^ | ||
+ | | schedticket_id | ||
+ | | tar_id | ||
+ | | account_id | ||
+ | | obs_num | ||
+ | | sched_from | ||
+ | | sched_to | ||
+ | | sched_interval_min | interval | ||
+ | | sched_interval_max | interval | ||
+ | |||
+ | ===== Using pyrts2 to preview schedules ===== | ||
+ | |||
+ | |||
+ | ====== Obtaining and modifying code ====== | ||
The GA scheduler code currently lives only in [[http:// | The GA scheduler code currently lives only in [[http:// |
code/ga_scheduling.txt · Last modified: 2009/01/18 00:00 (external edit)