-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
IndexError in day_ah_calc_optimum #89
Comments
I think the calculations of the baseloads went wrong.
First this all must be ok and until that moment you must:
|
clear and thanks. As i came from a somewhat older version i had to do two things
- create the baseload folder ( however unsure this had not happened yet ). When running the "bereken baseloads" from the gui. It stopped the optimization calculation and crashed. That issue is now resolved.
- I was indeed missing the scheduler options as that was not yet included in the file. In addittion i updated and added the baseload calculation options ( set use_baseloadcalc to false for now
- i ran the "berekenen baseloads". The 7 baseload files from the gui arer present and empty. No log file present.
will wait for the scheduler calculating the baseload to see if logfile is generated inc population of the 7 baseload files.
… On 18 Apr 2024, at 22:14, Cees van Beek ***@***.***> wrote:
I think the calculations of the baseloads went wrong.
Do you have installed samba on HA?
Then you can connect with a file explorer the share and folder
//addon_configs/xxxxxday_ahead_opt/daodata/baseloads
You should see 7 files: baseload_0.json ... baseload_6.json each about 218 bytes
When the baseload calculation has run (time set in scheduler??)) there must be a log of the run in:
//addon_configs/xxxxxday_ahead_opt/daodata/log
With content like:
Day Ahead Optimalisatie gestart: 18-04-2024 14:30:00 : calc_baseloads
Locatie: latitude 52.006443579881406 longitude:5.984225435624042
baseload voor weekdag 0 : [0.205, 0.392, 0.233, 0.494, 0.126, 0.129, 0.127, 0.178, 0.184, 0.366, 0.239, 0.256, 0.224, 0.208, 0.203, 0.235, 0.24, 0.675, 0.297, 0.256, 0.246, 0.191, 0.185, 0.159]
baseload voor weekdag 1 : [0.178, 0.437, 0.227, 0.555, 0.152, 0.136, 0.138, 0.172, 0.203, 0.378, 0.397, 0.377, 0.328, 0.318, 0.319, 0.247, 0.248, 0.803, 0.261, 0.222, 0.219, 0.216, 0.194, 0.164]
baseload voor weekdag 2 : [0.169, 0.487, 0.178, 0.674, 0.127, 0.131, 0.132, 0.198, 0.199, 0.173, 0.307, 0.192, 0.227, 0.298, 0.213, 0.234, 0.356, 0.908, 0.317, 0.247, 0.224, 0.22, 0.191, 0.185]
baseload voor weekdag 3 : [0.163, 0.501, 0.233, 0.628, 0.149, 0.135, 0.143, 0.176, 0.308, 0.377, 0.246, 0.283, 0.309, 0.254, 0.203, 0.218, 0.203, 0.656, 0.241, 0.269, 0.228, 0.214, 0.169, 0.182]
baseload voor weekdag 4 : [0.157, 0.441, 0.219, 0.567, 0.148, 0.154, 0.137, 0.186, 0.269, 0.283, 0.461, 0.471, 0.276, 0.251, 0.285, 0.244, 0.305, 0.473, 0.245, 0.234, 0.22, 0.176, 0.17, 0.159]
baseload voor weekdag 5 : [0.153, 0.387, 0.205, 0.463, 0.13, 0.126, 0.132, 0.17, 0.294, 0.276, 0.523, 0.325, 0.35, 0.427, 0.382, 0.24, 0.192, 0.447, 0.334, 0.287, 0.244, 0.205, 0.185, 0.18]
baseload voor weekdag 6 : [0.196, 0.394, 0.343, 0.436, 0.195, 0.13, 0.137, 0.197, 0.285, 0.245, 0.344, 0.384, 0.358, 0.325, 0.336, 0.327, 0.311, 0.507, 0.242, 0.286, 0.237, 0.21, 0.182, 0.16]
First this all must be ok and until that moment you must:
set `` "use_calc_baseload": "False"``` and
set your baseload in options.json
—
Reply to this email directly, view it on GitHub <#89 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/A3AUYCAIBNEVSQIS5IZ6WKTY6ASTFAVCNFSM6AAAAABGNREAWGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANRVGIYTCMBXHE>.
You are receiving this because you authored the thread.
|
adjusted the scheduler. Log did show up however baseload voor weekdagen X : [] <- all remain 'empty'
I did have the following observation but perhaps not relevant. Not sure if historical data is used but when i run the reports the following give me an internal server error:
- gisteren
- deze week
- deze maand
- dit jaar
- dit contract jaar
- 365 dagen
all others work and return a table
… On 18 Apr 2024, at 22:14, Cees van Beek ***@***.***> wrote:
I think the calculations of the baseloads went wrong.
Do you have installed samba on HA?
Then you can connect with a file explorer the share and folder
//addon_configs/xxxxxday_ahead_opt/daodata/baseloads
You should see 7 files: baseload_0.json ... baseload_6.json each about 218 bytes
When the baseload calculation has run (time set in scheduler??)) there must be a log of the run in:
//addon_configs/xxxxxday_ahead_opt/daodata/log
With content like:
Day Ahead Optimalisatie gestart: 18-04-2024 14:30:00 : calc_baseloads
Locatie: latitude 52.006443579881406 longitude:5.984225435624042
baseload voor weekdag 0 : [0.205, 0.392, 0.233, 0.494, 0.126, 0.129, 0.127, 0.178, 0.184, 0.366, 0.239, 0.256, 0.224, 0.208, 0.203, 0.235, 0.24, 0.675, 0.297, 0.256, 0.246, 0.191, 0.185, 0.159]
baseload voor weekdag 1 : [0.178, 0.437, 0.227, 0.555, 0.152, 0.136, 0.138, 0.172, 0.203, 0.378, 0.397, 0.377, 0.328, 0.318, 0.319, 0.247, 0.248, 0.803, 0.261, 0.222, 0.219, 0.216, 0.194, 0.164]
baseload voor weekdag 2 : [0.169, 0.487, 0.178, 0.674, 0.127, 0.131, 0.132, 0.198, 0.199, 0.173, 0.307, 0.192, 0.227, 0.298, 0.213, 0.234, 0.356, 0.908, 0.317, 0.247, 0.224, 0.22, 0.191, 0.185]
baseload voor weekdag 3 : [0.163, 0.501, 0.233, 0.628, 0.149, 0.135, 0.143, 0.176, 0.308, 0.377, 0.246, 0.283, 0.309, 0.254, 0.203, 0.218, 0.203, 0.656, 0.241, 0.269, 0.228, 0.214, 0.169, 0.182]
baseload voor weekdag 4 : [0.157, 0.441, 0.219, 0.567, 0.148, 0.154, 0.137, 0.186, 0.269, 0.283, 0.461, 0.471, 0.276, 0.251, 0.285, 0.244, 0.305, 0.473, 0.245, 0.234, 0.22, 0.176, 0.17, 0.159]
baseload voor weekdag 5 : [0.153, 0.387, 0.205, 0.463, 0.13, 0.126, 0.132, 0.17, 0.294, 0.276, 0.523, 0.325, 0.35, 0.427, 0.382, 0.24, 0.192, 0.447, 0.334, 0.287, 0.244, 0.205, 0.185, 0.18]
baseload voor weekdag 6 : [0.196, 0.394, 0.343, 0.436, 0.195, 0.13, 0.137, 0.197, 0.285, 0.245, 0.344, 0.384, 0.358, 0.325, 0.336, 0.327, 0.311, 0.507, 0.242, 0.286, 0.237, 0.21, 0.182, 0.16]
First this all must be ok and until that moment you must:
set `` "use_calc_baseload": "False"``` and
set your baseload in options.json
—
Reply to this email directly, view it on GitHub <#89 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/A3AUYCAIBNEVSQIS5IZ6WKTY6ASTFAVCNFSM6AAAAABGNREAWGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANRVGIYTCMBXHE>.
You are receiving this because you authored the thread.
|
Same issue here I think, no error when running calculate baseloads, but no data either;
Optimalisation calculation is running fine with hardcoded (fake) baseloads,
|
Thank you for sending this error-message. To better understand your situation can you give me some more information?
|
Thanks for trouble shooting!
It's working when using 2024-05-20 - today and stepwise adding april and may afterwards. I'm unfortunatelystill getting the same error when trying to open the reports-tab.
|
There is a logging page of the addon, which you can reach in HA; "Settings" / "Add-ons" / "Day-ahead-optimization" and then choice "Logbook" (in the right upper corner). |
Your min(time) is 1704063600. Converted: 1 january 2024 |
This is from the logs
I've downloaded everything between 1-4-2024 and 7-6-2024 now.
Still getting the same error, also on calc_optimum now
|
Apparently there are prognose data missing.
and the same query where you use da in place of temp? |
I believe so.
Price
SQL temp
SQL da
Also Logging van bewerking "Optimaliseringsberekening met debug":
Any way to check which list is out of range? Do I have another variable set wrong? |
Thank you for this information.
The baseload array is just 24 items and neads at least 30 items (just as the others). |
number of lines ([ and ] lines included)
logs
|
reconfigured baseload calc and setup all the entities. No issues in running calc before adding entities. Not sure yet why or how the below is related.
Traceback (most recent call last):
File "/root/dao/webserver/../prog/day_ahead.py", line 1911, in
main()
File "/root/dao/webserver/../prog/day_ahead.py", line 1872, in main
day_ah.calc_optimum()
File "/root/dao/webserver/../prog/day_ahead.py", line 1065, in calc_optimum
model += c_l[u] == c_t_total[u] + b_l[u] * hour_fraction[u] +
~~~^^^
IndexError: list index out of range
The text was updated successfully, but these errors were encountered: