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

Table should display ranges instead of known values #138

Open
KennethKinLum opened this issue Jun 8, 2020 · 3 comments
Open

Table should display ranges instead of known values #138

KennethKinLum opened this issue Jun 8, 2020 · 3 comments
Labels
enhancement New feature or request question Further information is requested

Comments

@KennethKinLum
Copy link
Contributor

KennethKinLum commented Jun 8, 2020

Version of the tool

v2.1.2-build.16

Describe the bug

Go to the new, blank page, and type in
Mon AM: 77
Tue PM: 157
Now the only possibility of 660 is Wed AM, so
type in
Wed AM: 206
and now all hope of 660 should be gone.

Would it be expected the graph doesn't show 660 any more? Or is the page being used in a way that is not supposed to?

Screen Shot 2020-06-08 at 3 14 13 AM

@KennethKinLum KennethKinLum added the bug Something isn't working label Jun 8, 2020
@elxris
Copy link
Owner

elxris commented Jun 9, 2020

HI @KennethKinLum!

I think you're using the tool as it's supposed to.

Yes, you had a possibility of 660 given that you didn't input Buy Price (which is important to give an accurate maximum).

But yeah, the algorithm tells us that you're on High Spike or Small Spike, but we can't predict exactly what value you will have as it's random. All we know is that it will be from 1.4 to 6 times your buy price.
In this case, as we don't know your buy price we will assume that it is 90 at minimum or 110 at maximum. So 1.4 * 90 = 126. 6 * 110 = 660. This gives us a range from 126 to 660.

I am sorry that we can't do more than that!

@elxris elxris closed this as completed Jun 9, 2020
@KennethKinLum
Copy link
Contributor Author

HI @KennethKinLum!

I think you're using the tool as it's supposed to.

Yes, you had a possibility of 660 given that you didn't input Buy Price (which is important to give an accurate maximum).

But yeah, the algorithm tells us that you're on High Spike or Small Spike, but we can't predict exactly what value you will have as it's random. All we know is that it will be from 1.4 to 6 times your buy price.
In this case, as we don't know your buy price we will assume that it is 90 at minimum or 110 at maximum. So 1.4 * 90 = 126. 6 * 110 = 660. This gives us a range from 126 to 660.

I am sorry that we can't do more than that!

The reason is that in the data table, it already doesn't show the 660, but in the graph, it still show it. I was wondering if the data table and the graph should match each other?

@elxris
Copy link
Owner

elxris commented Jun 9, 2020

Oh, this is a experience design thing, I thought that showing your input data it would be more useful when sharing screenshots of the table. Also improves mobile experience because a single number is shorter than a range. I’m keeping the graph as it is because that way we can feel how “lucky” we got.

But I’m open to hear other thoughts.

@elxris elxris reopened this Jun 9, 2020
@elxris elxris added enhancement New feature or request question Further information is requested and removed bug Something isn't working labels Jun 9, 2020
@elxris elxris changed the title [BUG] 77 and then 157, 206... then supposedly the graph won't have 660 any more? Table should display ranges instead of known values Jun 9, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request question Further information is requested
Projects
None yet
Development

No branches or pull requests

2 participants