We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
There is something to review here, probably I've a misunderstanding about the dragging process but can it be a bug.
It seems like the drag_key is defined based on the period of the previous gap iteration (the last gap period for the first iteration).
drag_key
Could it be that the correct period key to define is the one of the current iteration?
The affected method [suspect line 375]:
enerdata/enerdata/profiles/profile.py
Lines 346 to 395 in 4d89756
Proposal solution: Assign drag_key before period assignation (to exchange lines 375 and 376)
period
The text was updated successfully, but these errors were encountered:
Activate some debug data, to simplify reviewing of #87
7fd36dc
Fix possible BUG assigning drag period key. See #87
c1b5dfd
Fix #87
37025cf
Fix BUG assigning drag period key
1e05375
ecarreras
tinogis
XaviTorello
No branches or pull requests
There is something to review here, probably I've a misunderstanding about the dragging process but can it be a bug.
It seems like the
drag_key
is defined based on the period of the previous gap iteration (the last gap period for the first iteration).Could it be that the correct period key to define is the one of the current iteration?
The affected method [suspect line 375]:
enerdata/enerdata/profiles/profile.py
Lines 346 to 395 in 4d89756
Proposal solution:
Assign
drag_key
beforeperiod
assignation (to exchange lines 375 and 376)The text was updated successfully, but these errors were encountered: