search

meowmustard / mypersonalindex

Automatically exported from code.google.com/p/mypersonalindex
0 stars 0 forks source link

"nan" shares for some tickers after update. #26

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
What steps will reproduce the problem?
1. Open program to main screen

What is the expected output? What do you see instead?
I am getting "nan" number of shares for some of my securities.  This 
happened on Friday when I updated the prices during the day.

Nan stands for not a number, so something is getting corrupted in the 
calculation.  All of the data is still there and correct when I click edit.

What version of the product are you using? On what operating system?
Vista, 3.0

Please provide any additional information below.

I am able to add new securities correctly, but if the new one I add is the 
same, it doesn't work.  Example in my screenshot is VSS.  If I add VSS as a 
new line, it still shows nan shares.

In the screenshot, you can see SWSSX is working properly, but the other two 
lines are not.

If I uncheck "include in calculations" for the broken symbols, then the 
shares number becomes zero and the other calculations work.

Original issue reported on code.google.com by connor.s...@gmail.com on 19 Apr 2010 at 1:36

Attachments:

GoogleCodeExporter commented 8 years ago 
Hi Connor,

Thanks for reporting this bug!  I have two questions to help me identify the 
issue.

1. Can you go to the edit window for VSS, click "History ->", then on the right 
hand
side of the window choose "Splits" from the drop down and attach/paste the 
output if
it shows any?  My hunch is that there may be a "zero" split accidentally being
downloaded.  However, I was no able to produce this on my end using the same 
ticker
symbols.

2. Does this issue go away on Monday after you update the prices?

Thanks,
Matt

Original comment by mypersonalindex@gmail.com on 19 Apr 2010 at 5:48

GoogleCodeExporter commented 8 years ago 
Yes, you were correct.  It was a 0.00 split, with no date.  I was able to 
correct the problem by 
changing the "Download data from" parameter backwards one day and 
re-downloading all price data.  
I did it with the "download splits" box unchecked.  Not sure what difference 
that would have made.

On your second point, I did try updating prices on Saturday (after the markets 
were closed on 
Friday) and it did not fix the problem.

So I'm not sure what could have caused the problem, but an easy solution for 
you may be to ignore 
any 0.00 splits that are there to prevent the divide by zero error.

Let me know if I can help further.  Thanks!

Original comment by connor.s...@gmail.com on 19 Apr 2010 at 2:40

GoogleCodeExporter commented 8 years ago 
Thanks for the suggestion.  That is exactly what I'll do!  What I am thinking is
something changed briefly on Yahoo Finance that caused the issue, since when I 
tried
it yesterday and today, I cannot reproduce it.  You took the correct action to
redownload the prices.

I will now check that the split is not zero, or an "error" split.

Original comment by mypersonalindex@gmail.com on 19 Apr 2010 at 2:57

GoogleCodeExporter commented 8 years ago 
Yahoo Finance has changed their split date format and layout.  I am working on 
a fix
now, as it is impacting all securities.

Original comment by mypersonalindex@gmail.com on 24 Apr 2010 at 6:42

GoogleCodeExporter commented 8 years ago 
Ok, thanks.  Unchecking the "Download splits" button and redownloading data is 
a 
workaround for the meantime.

Original comment by connor.s...@gmail.com on 24 Apr 2010 at 7:01

GoogleCodeExporter commented 8 years ago 
Yes, but unfortunately causes issues if you own stock with splits.  For 
example, I
own BRK-B.  Since it split 50:1 in January, My Personal Index automatically
multiplied my shares by 50.  Since no splits are being downloaded, I would have 
to
manually adjust my shares to get accurate performance.  However, this fix isn't 
too
difficult, I just hope Yahoo Finance doesn't keep changing how their data is 
presented.

Original comment by mypersonalindex@gmail.com on 24 Apr 2010 at 7:11

GoogleCodeExporter commented 8 years ago 
The latest beta now fixes this issue.

Original comment by mypersonalindex@gmail.com on 29 Apr 2010 at 2:46