35s storage  Printable Version + HP Forums (https://archived.hpcalc.org/museumforum) + Forum: HP Museum Forums (https://archived.hpcalc.org/museumforum/forum1.html) + Forum: Old HP Forum Archives (https://archived.hpcalc.org/museumforum/forum2.html) + Thread: 35s storage (/thread123135.html) 
35s storage  Howard Lazerson  08252007 I was wondering if there was anyway to store and recall a series of numbers which represent coordinates of objects commonly observed thru a telescope. I wrote the alt/az pgm on this forum 8/20/07 and would like to put a list of about 100 objects numbered 1 thru 100 in memory. Since the pgm already uses up several alpha registers, I'm not sure how to do this. Each object notation will look like so; 1, 87.5, 56.2 ; The one [1]=object #1, 87.5= right ascenion, and 56.2= declination. This saves time having to refer to a list while observing. Any help would be appreciated, Thanks, Howard
Re: 35s storage  dbatiz  08252007 Have you considered saving the list in the following format: NNN.RRRDDD It would take a small subroutine to decode the object and make the components available to your program, but it shouldn't be too tricky. Depending on the indexing available, the index number could be the object number then you'd only have to decode RRR.DDD. Good luck Howard, I'd be interested to see your solution, Very respectfully,
David
Re: 35s storage  Alain Mellan  08252007 Quote:How about storing the data in 3D vectors? E.g. for the set above, use the sequence:
100 STO Iwill store a 3D vector in register 100. Then 1 STO+ I, and repeat... Hope that helps.
Edited: 25 Aug 2007, 7:46 p.m.
Re: 35s storage  Howard Lazerson  08252007 sounds reasonable, I will give it a try, thanks for the help, Howard
Re: 35s storage  Howard Lazerson  08252007 I never would have thought of that, will try that option also, thanks for your suggestion, Howard
Re: 35s storage  Earl Kubaskie  08252007 If you have a list with Item 2, Item 5, Item 203, Item 1425, etc. then Alain is right on the money. The vector method he advised especially allows you to use higher accuracy in your ascension/declination values than 1 decimal place.
But are your item numbers a continuous 1, 2, 3, ... etc. series? If so, your program could encode the item number into the register number, allowing the 3rd portion of the 3D vector to be used or reserved for additional data.
Re: 35s storage  Howard Lazerson  08252007 The item #s 1thru 100 each represent an object, the additionl numbers following that number represent its coordinates so when running the pgm if one wants to locate say object #39, there should be an easiy to rcl 39 , observe the values and then input these values either manually or with a subroutine into the pgm. Also n.n accuracy is sufficient for the coordinates. Thanks, Howard p.s. I have been using HP calculators for several years TO CALCULATE , programming them is new for me!
