update version #110
Merged
update version #110
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
peter-yuma
added a commit
that referenced
this pull request
Apr 28, 2025
* Update rewards to better handle ties (#109) * Update Staging (#100) (#101) * Enhancement/increased evaluation window (#91) * update the rewards to be calculated with the last 6 hours of predictions * make evaluation window a config option * update reward to properly get 6 hours of past data offset by one hour ago. * add completeness to rewards calculation * Just multiply the current rewards by the completeness score * remove config options and introduce constants for the evaluation window * release notes and version incremementing --------- Co-authored-by: Peter | Yuma, a DCG Company <[email protected]> * add function to handle tied weights * updated implementation * np nonzero instead of where * correct fn name --------- Co-authored-by: Matt | Yuma | DCG <[email protected]> * update version (#110) --------- Co-authored-by: Matt | Yuma | DCG <[email protected]>
Merged
peter-yuma
added a commit
that referenced
this pull request
Apr 30, 2025
* Update rewards to better handle ties (#109) * Update Staging (#100) (#101) * Enhancement/increased evaluation window (#91) * update the rewards to be calculated with the last 6 hours of predictions * make evaluation window a config option * update reward to properly get 6 hours of past data offset by one hour ago. * add completeness to rewards calculation * Just multiply the current rewards by the completeness score * remove config options and introduce constants for the evaluation window * release notes and version incremementing --------- Co-authored-by: Peter | Yuma, a DCG Company <[email protected]> * add function to handle tied weights * updated implementation * np nonzero instead of where * correct fn name --------- Co-authored-by: Matt | Yuma | DCG <[email protected]> * update version (#110) * Update date (#113) --------- Co-authored-by: Matt | Yuma | DCG <[email protected]>
peter-yuma
added a commit
that referenced
this pull request
Apr 30, 2025
* Rewards Changes (#111) * Update rewards to better handle ties (#109) * Update Staging (#100) (#101) * Enhancement/increased evaluation window (#91) * update the rewards to be calculated with the last 6 hours of predictions * make evaluation window a config option * update reward to properly get 6 hours of past data offset by one hour ago. * add completeness to rewards calculation * Just multiply the current rewards by the completeness score * remove config options and introduce constants for the evaluation window * release notes and version incremementing --------- Co-authored-by: Peter | Yuma, a DCG Company <[email protected]> * add function to handle tied weights * updated implementation * np nonzero instead of where * correct fn name --------- Co-authored-by: Matt | Yuma | DCG <[email protected]> * update version (#110) --------- Co-authored-by: Matt | Yuma | DCG <[email protected]> * Dev (#114) * Update rewards to better handle ties (#109) * Update Staging (#100) (#101) * Enhancement/increased evaluation window (#91) * update the rewards to be calculated with the last 6 hours of predictions * make evaluation window a config option * update reward to properly get 6 hours of past data offset by one hour ago. * add completeness to rewards calculation * Just multiply the current rewards by the completeness score * remove config options and introduce constants for the evaluation window * release notes and version incremementing --------- Co-authored-by: Peter | Yuma, a DCG Company <[email protected]> * add function to handle tied weights * updated implementation * np nonzero instead of where * correct fn name --------- Co-authored-by: Matt | Yuma | DCG <[email protected]> * update version (#110) * Update date (#113) --------- Co-authored-by: Matt | Yuma | DCG <[email protected]> --------- Co-authored-by: Matt | Yuma | DCG <[email protected]>
peter-yuma
added a commit
that referenced
this pull request
May 19, 2025
* Update rewards to better handle ties (#109) * Update Staging (#100) (#101) * Enhancement/increased evaluation window (#91) * update the rewards to be calculated with the last 6 hours of predictions * make evaluation window a config option * update reward to properly get 6 hours of past data offset by one hour ago. * add completeness to rewards calculation * Just multiply the current rewards by the completeness score * remove config options and introduce constants for the evaluation window * release notes and version incremementing --------- Co-authored-by: Peter | Yuma, a DCG Company <[email protected]> * add function to handle tied weights * updated implementation * np nonzero instead of where * correct fn name --------- Co-authored-by: Matt | Yuma | DCG <[email protected]> * update version (#110) * Rewards Changes (#111) * Update rewards to better handle ties (#109) * Update Staging (#100) (#101) * Enhancement/increased evaluation window (#91) * update the rewards to be calculated with the last 6 hours of predictions * make evaluation window a config option * update reward to properly get 6 hours of past data offset by one hour ago. * add completeness to rewards calculation * Just multiply the current rewards by the completeness score * remove config options and introduce constants for the evaluation window * release notes and version incremementing --------- Co-authored-by: Peter | Yuma, a DCG Company <[email protected]> * add function to handle tied weights * updated implementation * np nonzero instead of where * correct fn name --------- Co-authored-by: Matt | Yuma | DCG <[email protected]> * update version (#110) --------- Co-authored-by: Matt | Yuma | DCG <[email protected]> * Update date (#113) * Ensure intervals are evaluated across an hour of prices --------- Co-authored-by: Matt | Yuma | DCG <[email protected]>
Merged
peter-yuma
added a commit
that referenced
this pull request
May 19, 2025
* Update rewards to better handle ties (#109) * Update Staging (#100) (#101) * Enhancement/increased evaluation window (#91) * update the rewards to be calculated with the last 6 hours of predictions * make evaluation window a config option * update reward to properly get 6 hours of past data offset by one hour ago. * add completeness to rewards calculation * Just multiply the current rewards by the completeness score * remove config options and introduce constants for the evaluation window * release notes and version incremementing --------- * add function to handle tied weights * updated implementation * np nonzero instead of where * correct fn name --------- * update version (#110) * Rewards Changes (#111) * Update rewards to better handle ties (#109) * Update Staging (#100) (#101) * Enhancement/increased evaluation window (#91) * update the rewards to be calculated with the last 6 hours of predictions * make evaluation window a config option * update reward to properly get 6 hours of past data offset by one hour ago. * add completeness to rewards calculation * Just multiply the current rewards by the completeness score * remove config options and introduce constants for the evaluation window * release notes and version incremementing --------- * add function to handle tied weights * updated implementation * np nonzero instead of where * correct fn name --------- * update version (#110) --------- * Update date (#113) * Ensure intervals are evaluated across an hour of prices --------- Co-authored-by: Matt | Yuma | DCG <[email protected]>
peter-yuma
added a commit
that referenced
this pull request
Jun 16, 2025
* Update rewards to better handle ties (#109) * Update Staging (#100) (#101) * Enhancement/increased evaluation window (#91) * update the rewards to be calculated with the last 6 hours of predictions * make evaluation window a config option * update reward to properly get 6 hours of past data offset by one hour ago. * add completeness to rewards calculation * Just multiply the current rewards by the completeness score * remove config options and introduce constants for the evaluation window * release notes and version incremementing --------- * add function to handle tied weights * updated implementation * np nonzero instead of where * correct fn name --------- * update version (#110) * Rewards Changes (#111) * Update rewards to better handle ties (#109) * Update Staging (#100) (#101) * Enhancement/increased evaluation window (#91) * update the rewards to be calculated with the last 6 hours of predictions * make evaluation window a config option * update reward to properly get 6 hours of past data offset by one hour ago. * add completeness to rewards calculation * Just multiply the current rewards by the completeness score * remove config options and introduce constants for the evaluation window * release notes and version incremementing --------- * add function to handle tied weights * updated implementation * np nonzero instead of where * correct fn name --------- * update version (#110) --------- * Update date (#113) * Ensure intervals are evaluated across an hour of prices --------- Co-authored-by: Matt | Yuma | DCG <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.