In order to join the daily format quickly, I would need a submission window of 90-120 min …
2 Likes
The main reason I do not submit daily rounds is disappointment. Instead of making daily tournaments appealing due to a higher potential earning, Numerai decided to take the other direction and make the weekly tournament less remunerative (70% of the current payout) so that users must do more to get almost the same. I do not like this approach at all.
6 Likes
What’s the problem with int8? Can’t you download any dataset you want from compute?
Any update on accepting delayed submissions automatically for D+1? I have a few models which take way longer and I think this would really help/motivate me to participate in daily rounds.
1 Like
I am seeing an error for my daily submissions on numerapi 2.9.4
2022-11-09 13:38:07,147 ERROR numerapi.base_api: You must provide predictions for the current live IDs. Make sure you are using the latest live data.
Even though i am downloading round 351 tournament data.
Downloading numerai_tournament_data_351.parquet ⠙
Is anyone facing this issue as well?
You need to download numerai_live_data.parquet instead. numerai_tournament_data only gets updated weekly.
1 Like
i am pretty confused with all impacts after daily tournament started: no more daily/monthly/annual gain. weekly submission result was disconnected. no daily submission return estimation, etc. not sure how soon every will be back to normal.
3 Likes
Pretty sure all the functionality will return, it’s just going to take a little bit. The jump to daily put a massive load on the data-base. I think once they get things optimized we’ll see that data reappear.
We turned off returns because we thought daily rounds might be polluting the numbers (they were not) and the current returns numbers are not easily verifiable from the outside. We are doing some more validation before re-enabling (soon).
The current Numerai and Signals returns calculations live in separate pipelines with their own bespoke implementations. The code is complex and hard to debug because it essentially boils the ocean from the beginning of time re-simulating every tournament scoring change, recalculating every payout, multiplier change, etc to derive returns.
Returns will return soon, and I will publish an accompanying worksheet explaining how users can audit/verify 1d, 3mo & 12mo returns using Excel themselves.
Thanks for your patience.
8 Likes
@wigglemuse You can in compute-heavy. You cannot in compute-light. That is what I desire. I have been complaining about it in all the channels (RC, the Trello, now here) without any success so far.
Hmmm…makes no sense to me, but I guess I don’t understand it. You’ve got an environment right, can’t it just do any arbitrary internet (and therefore api) call you want? If I can download int8 outside of compute why can’t you do it inside? What is actually stopping you?
no, in compute-light you do not have an evironmanet, but you deploy a pickled model file, the version of data (v2,3,4) and the list of features the model expects to the numerai endpoint. The rest is handled by numerai.
The models predict method is called during live with a pd.DataFrame of the data. That’s it.
That being said, I could of course start my predict method by ignoring the passed data, creating an API link and downloading the data. Apart from technical issues (can the script write to where it is running??) that completely defeats the compute-light goal of maximum integration so what I am asking for is to have another deployment parameter for int8 or float data.
1 Like
Yeah, ok, pretty limited. I’m not saying they shouldn’t have int8 (and I’d need a whole lot more than that to make compute workable), but seems like you could get around it in the meantime as well. Can you just multiply the data * 4 to convert to int or does that cause memory issues?
any idea when the staking for daily tournament will be started ?
2 Likes
thank you for that tip. That is a reasonable workaround. I will try to do it that way!
When does the Friday round opens? I am getting ‘ValueError: Current round not open for submissions’
see it just opened, must be more patient. missing indication in gui
up ! I think this would be good to give an end this in-between period…
Please start daily payouts !
Recognized that daily submission timeslot was changed. Like yesterday, the notification email was received at 1:43AM (GMT8), comparing with original schedule - 9PM (GMT8).
May i know this is temporary arrangement for test or there will be new fixed timeslot for data submission ?
MAJOR BUG REPORT:
How come that numerapi check-new-round --hours 1 returns 0 , except at the critical times after 13:00 UTC, when we need it to test for 1 to know when to start processing? But, then it just generates a whole stack of errors, making it useless and the daily tournaments opening times undetectable. It has been like this for the last two tournaments. Combined with the fact that you keep changing the opening times, it makes the daily tournaments totally impractical to participate in.
If you want us to be detecting the opening times, you must provide a functioning CLI test, not something buggy like this. If you are doing this to force us into using ‘compute’, then I am out of here. I am not willing to struggle with the complexities of AWS and pay for the ‘privilege’ when I have a perfectly functioning automation of my own. Or at least I had one …
2 Likes