IMPORTANT: Change to run_daily_price_updates in version 1.48

[robcarver17]

For reasons discussed in #913 I have broken out two new run_ processes, so there are now three:

• run_daily_prices: just does historical contract prices
• run_daily_fx_and_contract_updates: does update_sampled_contracts and update_fx_prices
• run_daily_update_multiple_adjusted_prices: does what it says on the tin.

The effect of this is that you will need to add lines to your crontab to run the two relevant new processes, example here. I recommend running run_daily_fx_and_contract_updates early in the morning as it is not time sensitive, and running run_daily_update_multiple_adjusted_prices in late evening.

EDIT: Under linux, don't forget to set execution permissions on the two new script files chmod +x run_daily_update_multiple_adjusted_prices and run_daily_fx_and_contract_updates', or the crontab won't run them.

You may also want to modify your control_config.yaml; I have added defaults here. Here is an excerpt from mine, with notes:

process_configuration_start_time:
  run_daily_prices_updates: '13:00'
  run_daily_fx_and_contract_updates: '07:00'
  run_daily_update_multiple_adjusted_prices: '23:00'
process_configuration_stop_time:
  run_daily_prices_updates: '23:30'
  run_daily_fx_and_contract_updates: '23:30'
  run_daily_update_multiple_adjusted_prices: '23:30'
process_configuration_previous_process:
#  run_daily_prices_updates: 'run_daily_fx_and_contract_updates' ## optional, I don't bother with this dependency
#  run_daily_update_multiple_adjusted_prices: 'run_daily_prices_updates' ## optional, I don't have this dependency as I'm worried about running out of time I always want to update my multiple and adjusted prices
  run_systems: 'run_daily_update_multiple_adjusted_prices' 
  run_strategy_order_generator: 'run_systems'
  run_cleaners: 'run_strategy_order_generator'
  run_backups: 'run_cleaners'
  run_reports: 'run_strategy_order_generator'
# we include every method to make process monitoring easier
process_configuration_methods: 
  run_daily_prices_updates:
    update_historical_prices:
      max_executions: 1
  run_daily_fx_and_contract_updates:
    update_fx_prices:
      max_executions: 1
    update_sampled_contracts:
      max_executions: 1
  run_daily_update_multiple_adjusted_prices:
    update_multiple_adjusted_prices:
      max_executions: 1

I'd recommend not pulling this change for a couple of days until I've tested it.

[meldinman]

Thanks for updating this, just curious, are you running systems before updating multiple adjusted prices? Wouldn't that be delaying the system by a day?

[robcarver17]

No I run systems afterwards. The first active line in the previous process .yaml config makes that happen.

[meldinman]

I see that, I guess the time you put for earliest start on the sample snippet is not what your using (23:00).
Do you think its ok to be running run_daily_fx_and_contract_updates in the morning while stack handler is also running?

[robcarver17]

Yes. FX prices aren't used by the stack handler, and contract expiry date updates aren't eithier (there might be a corner case where IB change the expiry date of a contract that will affect the continous checking of broker and database contract positions, but that is already a potential problem).

[emretezel]

When using the interactive_controls tool, shouldn't one be able to change the status (Go/Stop) of the new processes, run_daily_fx_and_contract_updates and run_daily_update_multiple_adjusted_prices ? Don't see them under option 4 then 40

run_backups                     Started 03/31 21:15:03 ended 03/31 21:28:43 Status STOP    PID 0.0      not running
run_capital_update              Started 03/31 20:31:03 ended 03/31 20:31:10 Status STOP    PID 0.0      not running
run_cleaners                    Started 03/31 21:29:04 ended 03/31 21:29:18 Status STOP    PID 0.0      not running
run_daily_prices_updates        Started 03/31 00:05:04 ended 03/31 20:30:19 Status STOP    PID 0.0      not running
run_reports                     Started 03/31 21:25:04 ended 03/31 21:33:44 Status STOP    PID 0.0      not running
run_stack_handler               Started 03/31 00:01:04 ended 03/31 20:30:00 Status STOP    PID 0.0      not running
run_strategy_order_generator    Started 03/31 21:00:03 ended 03/31 21:00:04 Status STOP    PID 0.0      not running
run_systems                     Started 03/31 20:45:02 ended 03/31 20:47:50 Status STOP    PID 0.0      not running

[tgibson11]

Good point. I won't yell at you if you create an issue for this one 😀

[oldlore]

Hmm they all show up for me in 4->40 or 4->43. I haven't tried to change the status yet. Maybe they have to run once before the list is populated?

[emretezel]

i also notice once they run they show on interactive controls

[tgibson11]

Also a good point. I haven't actually looked.

[tgibson11]

Yes, they do show up for me, so I'm sure @oldlore is right - it's just a matter of needing to run them once.