Open o355 opened 6 years ago
Now working on this issue, ETA is next week.
At this point, we have a few different loop config variables, all in the UI section.
detailedinfoloops
controls 1.5-day hourly & 10-day hourly, historical & yesterday hourly, hurricane detailed info, and tide info.forecast_detailedinfoloops
controls the 10-day hourly forecast.alerts_usiterations
controls US alert info.alerts_euiterations
controls EU alert info.The new hope is for every data type to have their own unique variable.
hourlyinfo_iterations
- Controls 1.5 day/10 day hourly, 2 by defaultforecastinfo_iterations
- Controls 10 day forecast, 3 by defaulthurricaneinfo_iterations
- Controls hurricane detailed info, 2 by default. This default number will likely change during QA.tideinfo_iterations
- Controls tide detailed info, 6 by default.historicalhourly_iterations
- Controls historical hourly info, 2 by default.yesterdayhourly_iterations
- Controls yesterday hourly info, 3 by default.alertsus_iterations
- Controls US alert info, 1 by default.alertseu_iterations
- Controls EU alert info, 2 by default.Now modifying the todo list, ETA for fix is 6/8.
Now working on PyWeather to read the new variables.
If you have an indev copy of PyWeather and git pull it'll be broken for a few days.
Also while we're working with the config loading part of code let's make sure that occurred.
is moved to the 1st line of print and not the 2nd.
Oh and let's also completely redo the entire logger section for config variables
Finished up with coding for reading the variables.
Now on to other various stuff.
I make sure that print statements looked good.
Refactoring all the config logger statements then back to the ACTUAL plan.
New ETA for completion is this weekend
Confusing title, but the TL;DR is that there's 1 config value for setting iterations for a lot of data types. We need to separate them all out.
To do list: