haileyhalimj@gmail.com commited on
Commit
60e5fc6
Β·
1 Parent(s): 07cab60

Fix: Remove set_global_dates call from config_page.py

Browse files

- Dates are now handled via optimization_config.get_date_span()
- Extract functions take start_date as parameter directly
- No global date setting needed

Files changed (1) hide show
  1. config_page.py +4 -4
config_page.py CHANGED
@@ -1063,10 +1063,10 @@ def clear_all_cache_and_results():
1063
  calculated_end_date = st.session_state.start_date + timedelta(days=4)
1064
  planning_days = 5
1065
 
1066
- sys.path.append('src')
1067
- import src.preprocess.extract as extract
1068
- extract.set_global_dates(st.session_state.start_date, calculated_end_date)
1069
- st.write(f"πŸ“… Updated global dates: {st.session_state.start_date} to {calculated_end_date} ({planning_days} days)")
1070
 
1071
  st.success("βœ… All caches and previous results cleared!")
1072
 
 
1063
  calculated_end_date = st.session_state.start_date + timedelta(days=4)
1064
  planning_days = 5
1065
 
1066
+ # Note: Dates are handled directly in optimization_config.py via get_date_span()
1067
+ # No need to set global dates - extract functions take start_date as parameter
1068
+ st.write(f"πŸ“… Date configuration: {st.session_state.start_date} to {calculated_end_date} ({planning_days} days)")
1069
+ st.info("πŸ’‘ Dates will be applied when optimization runs (via optimization_config.get_date_span())")
1070
 
1071
  st.success("βœ… All caches and previous results cleared!")
1072