Skip to content
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

Impossible pattern? #82

Closed
rssteffey opened this issue Apr 13, 2020 · 15 comments
Closed

Impossible pattern? #82

rssteffey opened this issue Apr 13, 2020 · 15 comments
Labels
prediction Prediction / Calculation Issues

Comments

@rssteffey
Copy link

rssteffey commented Apr 13, 2020

I purchased my turnips yesterday for 104 apiece. This morning (Monday AM) they were 97, and now (Monday PM) they are 92.

I am 100% positive these are the correct prices, but the app has no patterns that allow for 92 right now if I purchased at 104 yesterday. Is this a floating point case or have I screwed up using it?

(Understood if it may be hard to solve from this minimal case, but it may help as a data point for another issue. This is also my third week in the stalk market, so I don't think anything special applies)

@theRTC204
Copy link
Collaborator

Seems like the same off-by-one rounding error that has been reported in several other issues already. There are several patterns available if you change your Monday PM price to 93 Bells.

@ZZZZzzzzac ZZZZzzzzac mentioned this issue Apr 14, 2020
@mikebryant
Copy link
Owner

Working through the cases...

0/fluctuating:
decreasing phase max is ceil(0.8104) == 84, therefore the 97 and 92 would both have to be high phase.
high phase min is ceil(0.9
104) == 94, so that rules out the 92

1/high spike
first value would need to be 94 or less

2/decreasing
First value 94 or less again

3/small spike
first value 94 or less if decreasing
But this can be the peak, so
first value is in range of 94 to 146
But then second value needs to be in the same range, and it's not

@mikebryant
Copy link
Owner

@rssteffey And to confirm, this is definitely the buy price on your own island, not the price you bought the turnips for elsewhere?

@mikebryant mikebryant added the prediction Prediction / Calculation Issues label Apr 14, 2020
@rssteffey
Copy link
Author

Correct. All three prices were local to my island (I did visit a friend and buy an additional few stacks of turnips for <100, but I didn't think that affected my local prices)

They are 88 now (Tuesday morning)

@jpblanton
Copy link

I'm having a similar issue. Bought at 107 on Sunday, prices went 115 -> 91 -> 157 as of Tuesday morning. If I remove the Sunday price it shows patterns, but the max predicted Sunday price in those patterns is only 102

@mikebryant
Copy link
Owner

@rssteffey This should be fixed now

@jpblanton What're your prices like today?

@beastboy92
Copy link

I also have a similiar issue. Since yesterday I have a Nook's cranny and started to monitor my turnip prices. When I put in my data (first time buyer: Yes, Tue AM: 105, Tue PM: 113, Wed AM:120 and Wed PM: 81) I don't get any patterns. Can this be because I only started getting prices yesterday?

@jpblanton
Copy link

@mikebryant 167 Tuesday PM, 133 today. Which was in line with what the system put out when I left the starting price blank

@mikebryant
Copy link
Owner

@beastboy92 Can you try again? You might have been hit by a brief blip that was fixed in #113 - I see a pattern for you right now when I try

@mikebryant
Copy link
Owner

@jpblanton Just to check, because you didn't say - That buy price is on your own island? And it's not the first week someone who lives on your island has bought from daisy on your island?

Because your data matches perfectly with a lower buy price, which is what happens if you're a first time buyer

@jpblanton
Copy link

It's the first time I've purchased them; the third Sunday overall. And yes, all my island

@mikebryant
Copy link
Owner

@jpblanton Then I don't think there's a problem - as it says on the site, if it's the first time you're buying them on your own island you need to check the first time buyer option, which disables the buy input. (because it makes a hidden buy price instead and uses that to compute)

@mikebryant
Copy link
Owner

@jpblanton This is your prediction: https://turnipprophet.io/?prices=.115.91.157.167.133&first=true
The hidden buy price was somewhere between 90 and 99.

@jpblanton
Copy link

jpblanton commented Apr 15, 2020 via email

@mikebryant
Copy link
Owner

No problem. Hope you find the site useful in future! :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
prediction Prediction / Calculation Issues
Projects
None yet
Development

No branches or pull requests

5 participants