Constants aren't so constant [SOLVED]

12032016, 04:14 PM
(This post was last modified: 02022018 09:11 PM by JMB.)
Post: #1




Constants aren't so constant [SOLVED]
The physical constants that can be accessed in the Prime, fall mainly into two categories: constants with an exact value (like "c"  the speed oh light), and constants whose values depend on the current state of the art measurements (like "G"  the gravitation constant).
The internationally recommended values are recorded by CODATA (Committee on Data for Science and Technology). These constants can also be browsed at NIST (National Institute of Standards and Technology). As long as I've seen, the values stored in the Prime agree exactly with the values given in 2010 by CODATA (for example, G=6.67384E11). Today these values are dated, because a new set of values was stablished in 2014 (for example, te current value for G is: 6.67408E11). Given the above, I propose to HP considering the update of these values in a future firmware release. 

12052016, 03:26 PM
(This post was last modified: 12052016 03:27 PM by Tim Wessman.)
Post: #2




RE: Constants aren't so constant
(12032016 04:14 PM)JMB Wrote: Today these values are dated, because a new set of values was stablished in 2014 (for example, te current value for G is: 6.67408E11). I'd be happy to do so, but it is a pretty low priority item at this point. The thing that takes the longest is simply going through the table and finiding which did or didn't change. If you wanted to point those out, I'd be much more likely to be able to resolve sooner rather then later. Thanks! Here's the actual code table: Code: /// These values come from the NIST 2010 published values TW Although I work for the HP calculator group, the views and opinions I post here are my own. 

12052016, 04:30 PM
(This post was last modified: 12052016 04:34 PM by sat1410.)
Post: #3




RE: Constants aren't so constant
I used the 2014 CODATA values in http://physics.nist.gov/cuu/Constants/Ta...lascii.txt
In cases where there were a different number of digits in the NIST vs. existing HP code, I used NIST values. Also, one small error noted in the pdf manual on the HP support site (2nd edition, Sept 2016, DPN 813269002): Under the list on constants on page 499, in the chemistry section, the manual says "Boltmann, k" as one of the constants. Should be 'Boltzmann' (z is missing). Hope these quick changes are useful. Code: /// These values come from the NIST 2014 published values 

12052016, 04:54 PM
Post: #4




RE: Constants aren't so constant
Definitely, I can do a text compare and cross check much easier. Much appreciated!
TW Although I work for the HP calculator group, the views and opinions I post here are my own. 

12052016, 05:21 PM
Post: #5




RE: Constants aren't so constant
I agree with the new values listed by sat1410.
Thanks to everyone. 

12052016, 06:09 PM
Post: #6




RE: Constants aren't so constant
I would also suggest adding NIST_Year or something, to identify in one place which version of all the variables you have  to be accessible from a user program along with the other variables, so that a program can add "as at 2016" or whatever to the small print..
Everyone is bound to have their own additions they would like to sneak in, but I usually end up defining my own, if only whilst compatability testing. Stephen Lewkowicz (G1CMZ)... USA's changing goals In 1960s, delivering a man to the Moon... In 2020s, delivering a vote to the electors. 

01142018, 12:48 PM
(This post was last modified: 01142018 12:49 PM by JMB.)
Post: #7




RE: Constants aren't so constant
The last FW beta v3 (13217) still has the old values. Is there any possibility to see the new values for the constants in the final version?


01152018, 04:12 AM
Post: #8




RE: Constants aren't so constant
A Murphy's law corollary states that "Constants aren't, and variables won't." Such is the dichotomy between nature and frustrated programmers....


01152018, 03:46 PM
Post: #9




RE: Constants aren't so constant
(01152018 04:12 AM)JimP Wrote: A Murphy's law corollary states that "Constants aren't, and variables won't." Such is the dichotomy between nature and frustrated programmers.... Nice. Wikis are great, Contribute :) 

01152018, 04:43 PM
Post: #10




RE: Constants aren't so constant
(12032016 04:14 PM)JMB Wrote: The physical constants that can be accessed in the Prime, fall mainly into two categories: constants with an exact value (like "c"  the speed oh light), and constants whose values depend on the current state of the art measurements (like "G"  the gravitation constant). But even constant speed of light isn't as constant since it depends on the medium it travels. In water (I suppose 20° celsius) it's 225 e6 m/s, in glass it's 160 e6 m/s. HP: 20S 25C 32S 33E 33s 35s 41CV 42S 39GS 48SX 71B Casio: FX702P Swissmicros: DM15L Need Forth71B 

01162018, 05:12 PM
Post: #11




RE: Constants aren't so constant
Just note that Rinf will be "109737315685" since we are limited to 12 digits of precision here. Anyway...
TW Although I work for the HP calculator group, the views and opinions I post here are my own. 

01162018, 07:01 PM
Post: #12




RE: Constants aren't so constant
Understood Tim, thanks.


02022018, 09:12 PM
Post: #13




RE: Constants aren't so constant [SOLVED]
Corrected in firmware 13333.
Thanks to the HP Prime Team! 

« Next Oldest  Next Newest »

User(s) browsing this thread: 1 Guest(s)