Are US units correct?
|
05-20-2015, 05:32 AM
(This post was last modified: 05-20-2015 05:36 AM by Joe Horn.)
Post: #1
|
|||
|
|||
Are US units correct?
According to the HP 50g's unit conversion utility, these are true:
1 chain = 4 rods = 66 ftUS 1 fath (fathom) = 6 ftUS But Prime gives these conversions: 1 chain = 4 rods = 65.9999999982 ftUS 1 fath = 5.99999999984 ftUS Perhaps it's all based on this difference: 1 meter = 3.28083333333 ftUS (HP 50g) 1 meter = 3.28083333324 ftUS (HP Prime) Which is correct? EDIT: Something is clearly amiss in the Prime. It says: 1 miUS = 5279.99999983 ftUS But in actuality 1 miUS = exactly 5280 ftUS. It looks like Prime's definition of ftUS is screwed up. <0|ɸ|0> -Joe- |
|||
05-20-2015, 05:49 AM
Post: #2
|
|||
|
|||
RE: Are US units correct?
and this doesn't fix it.
Oh well. |
|||
05-20-2015, 06:39 AM
Post: #3
|
|||
|
|||
RE: Are US units correct? | |||
05-20-2015, 08:52 AM
Post: #4
|
|||
|
|||
RE: Are US units correct? | |||
05-20-2015, 09:01 AM
Post: #5
|
|||
|
|||
RE: Are US units correct?
(05-20-2015 06:39 AM)petaks01 Wrote: Nothing converts to "in" on my calc.It's because you're in CAS mode, see this thread for more details about this issue. |
|||
05-20-2015, 09:32 AM
Post: #6
|
|||
|
|||
RE: Are US units correct? | |||
05-20-2015, 09:49 AM
Post: #7
|
|||
|
|||
RE: Are US units correct?
When I saw the title "Are US units correct?", first reaction was "of course not!" before I understood it was related to a possible issue on the Prime. I noticed that in Star Trek TNG they are all metric, seems like the future is already known ;-)
|
|||
05-20-2015, 10:23 AM
Post: #8
|
|||
|
|||
RE: Are US units correct?
(05-20-2015 09:01 AM)Didier Lachieze Wrote:(05-20-2015 06:39 AM)petaks01 Wrote: Nothing converts to "in" on my calc.It's because you're in CAS mode, see this thread for more details about this issue. Quite right, I'm an idiot - Why on Earth would I want to convert to in in CAS mode? |
|||
05-20-2015, 10:40 AM
Post: #9
|
|||
|
|||
RE: Are US units correct?
This idiot expected the basic prefix and unitconversions to be available in all three modes (CAS/RPN/textbook) as the menus are accessible.
|
|||
05-20-2015, 11:37 AM
Post: #10
|
|||
|
|||
RE: Are US units correct?
Yep UNITS still needs some work.
It would be nice if you could use units with variables. abc_cm for example. Seems to throw errors. |
|||
05-20-2015, 12:11 PM
Post: #11
|
|||
|
|||
RE: Are US units correct? | |||
05-20-2015, 01:28 PM
(This post was last modified: 05-20-2015 01:32 PM by CR Haeger.)
Post: #12
|
|||
|
|||
RE: Are US units correct?
(05-20-2015 12:11 PM)DrD Wrote: Since variables are used to store objects, you can store objects (with units) in variables: Thank you for that reminder which is useful if you know in advance that you want the variable to be stored as a _unit object. What I was referring to was taking a variable with say a real value (2.0) then converting it into a _unit object. In this case, it seems you need to do the following: Vars (enable Value soft-key) User abc --> 2.0 Units Length cm --> 2.0_cm I forgot about the Value soft-key... EVAL(abc) Units Length cm also works... |
|||
05-20-2015, 02:16 PM
Post: #13
|
|||
|
|||
RE: Are US units correct?
Inside the CAS, all derived units are stored using the MKSA system. This of course can lead to some small rounding errors in conversions from US units to US units, it's unavoidable (and in is a reserved word inside the CAS, so that you can loop in a list, you must use inch for the unit. Since inch is not a metric unit, it has no real reason to have a reserved word).
The list of derived units follows, if you find something wrong, please correct First number is a numeric factor, remainding numbers are powers of meter, kilogram, second, Ampere, Kelvin, mol, candela, last column is reserved for currency conversions. Code:
|
|||
05-20-2015, 04:58 PM
Post: #14
|
|||
|
|||
RE: Are US units correct? | |||
05-20-2015, 05:45 PM
Post: #15
|
|||
|
|||
RE: Are US units correct?
(05-20-2015 04:58 PM)David Hayden Wrote:(05-20-2015 02:16 PM)parisse Wrote: const mksa_unit __ftUS_unit={0.304800609601,1,0,0,0,0,0,0,0};This looks wrong to me. An inch is now defined as exactly 25.4mm which means one foot is exactly 0.3048m That is the us survey foot which is 1200⁄3937m There was a missing 0 in the definition so it read ..61 instead of ..601 at the end. TW Although I work for HP, the views and opinions I post here are my own. |
|||
05-20-2015, 06:44 PM
Post: #16
|
|||
|
|||
RE: Are US units correct? | |||
05-21-2015, 05:57 AM
(This post was last modified: 05-21-2015 05:57 AM by parisse.)
Post: #17
|
|||
|
|||
RE: Are US units correct?
Does it mean that _ft and _ftUS should be the same (then why not remove _ftUS)? It would make more sense to keep _ftUS!=_ft, but I don't really care... I just don't want to loose too much time on this!
|
|||
05-21-2015, 06:53 AM
(This post was last modified: 05-21-2015 07:01 AM by Thomas_Sch.)
Post: #18
|
|||
|
|||
RE: Are US units correct?
(05-20-2015 06:44 PM)Thomas_Sch Wrote: nice finding: Any comments to the strong output? My fault, or a new error in the Prime? Thanks. Edit: the last line in the screenshot hat been my original input, I get this, if I select the crazy line above and press the soft key COPY . - Why the Prime converts "inch" to these chinese characters? - How should the input to obtain a correct conversion to inch within CAS mode? The Prime does habe the last firmware, language is set to english. |
|||
05-21-2015, 07:59 AM
Post: #19
|
|||
|
|||
RE: Are US units correct?
The physical calc doesn't show the "chinese" tail.
Only this: CONVERT(1_km,1_) "Error: Inconsistent units" My guess is that it strips the inch part from the input before trying to convert and gets really confused as the "in" is a reserved word in CAS based on a previous post here. I sure would like a working conversion/units/prefix part and if we have to skip the "in" and use "inch" everywhere thats fine with me. |
|||
05-21-2015, 11:34 AM
Post: #20
|
|||
|
|||
RE: Are US units correct?
(05-21-2015 07:59 AM)petaks01 Wrote: The physical calc doesn't show the "chinese" tail. On the physical calculator, in CAS mode, typing Code: CONVERT(1_(km),1_(inch)) But typing Code: convert(1_(km),1_(inch)) However, copying this command back into the entry line gives Code: convert(1_(km),1_(inch)) Using the "Sto->" key like this: Code: 1_(m)->_inch However, Code: 1_(m)->1_(inch) The only definite bug that I have found is the non-display of "inch". However, I feel that the system could be more forgiving of variant input than in fact it is. Nigel (UK)[/code] |
|||
« Next Oldest | Next Newest »
|
User(s) browsing this thread: 5 Guest(s)