WP43 News

This area is for discussion about these families of custom high-end Scientific Calculator applications for SwissMicros devices.
emece67

Re: 43S News

Post by emece67 »

Hi,

Happy to know that there's so much work in progress on this project.

I'm curious about the U-> menu at g+6, what is it intended for?

In the list of data types, there are no "units". Will this machine support units à la 48/49/50?

Thanks & regards.
User avatar
Walter
Posts: 3070
Joined: Tue May 02, 2017 11:13 am
Location: On a mission close to DRS, Germany

Re: 43S News

Post by Walter »

Walter wrote:
Sat Mar 03, 2018 3:32 pm
Menu names should be self-explanatory except U-> for unit conversions and L-> for angular conversions.
(emphasis added)

And about units, please allow me quoting the draft manual:
There is absolutely no need to enter units in your calculations. Just stay with a coherent set of units while calculating and you will get meaningful results within this set (the big advantage of SI is that it is the largest coherent set of units available on this planet). If you need to convert special inputs into units being part of such a set or you require results expressed in special units, however, [U->] or [L->] will help.
HTH, else continue asking.
WP43 SN00000, 34S, and 31S for obvious reasons; HP-35, 45, ..., 35S, 15CE, DM16L S/N# 00093, DM42β SN:00041
emece67

Re: 43S News

Post by emece67 »

Walter wrote:
Sat Mar 17, 2018 6:20 pm
nd about units, please allow me quoting the draft manual:
There is absolutely no need to enter units in your calculations. Just stay with a coherent set of units while calculating and you will get meaningful results within this set (the big advantage of SI is that it is the largest coherent set of units available on this planet). If you need to convert special inputs into units being part of such a set or you require results expressed in special units, however, [U->] or [L->] will help.
HTH, else continue asking.
Unfortunately, many times, I cannot stay within a coherent set of units while calculating, so I will continue asking. Will it support commands equivalent to CONVERT, UBASE & UFACT in such machines? In case you have not used such commands:
  • UBASE: converts one quantity in some units to the SI. E.g. from 1_pc/yr (parsec/year) one gets 977 813 106_m/s
  • CONVERT: converts one quantity in some units to other units. E.g. from 1_pc/yr (parsec/year) and 1_knot one gets 1.90071662E9_knot
  • UFACT: factors one quantity in some units to be expressed in terms of other unit. E.g. from 1_pc/yr and 1_mi (mile) one gets 607584.8954605_mi/s
Thanks & regards,
User avatar
Walter
Posts: 3070
Joined: Tue May 02, 2017 11:13 am
Location: On a mission close to DRS, Germany

Re: 43S News

Post by Walter »

emece67 wrote:
Sat Mar 17, 2018 11:42 pm
Walter wrote:
Sat Mar 17, 2018 6:20 pm
And about units, please allow me quoting the draft manual:
There is absolutely no need to enter units in your calculations. Just stay with a coherent set of units while calculating and you will get meaningful results within this set (the big advantage of SI is that it is the largest coherent set of units available on this planet). If you need to convert special inputs into units being part of such a set or you require results expressed in special units, however, [U->] or [L->] will help.
HTH, else continue asking.
Unfortunately, many times, I cannot stay within a coherent set of units while calculating, so I will continue asking. Will it support commands equivalent to CONVERT, UBASE & UFACT in such machines? In case you have not used such commands:
  • UBASE: converts one quantity in some units to the SI. E.g. from 1_pc/yr (parsec/year) one gets 977 813 106_m/s
  • CONVERT: converts one quantity in some units to other units. E.g. from 1_pc/yr (parsec/year) and 1_knot one gets 1.90071662E9_knot
  • UFACT: factors one quantity in some units to be expressed in terms of other unit. E.g. from 1_pc/yr and 1_mi (mile) one gets 607584.8954605_mi/s
Let's see what's provided already solving your problems - {...} embraces softkeys:

1 pc/yr = pc/m / (yr/s) x 1 m/s , so you may key in:

Code: Select all

1 [g] [U->] {x:} {pc->m}      returns 3.085 68x10^16
[EXIT]                        returns the top view of [U->].
1 {year->s} [/]               returns 9.778 13x10^8 m/s immediately. Store it, e.g. via 
[STO] 00
1 knot = 1 nmi/h = nmi/m / (h/s) x 1 m/s , so continue:

Code: Select all

{x:} [f] {nmi.->m}    returns 1 852
60 [g] [x²] [/]       returns 0.514 44 m/s directly. Thus,
[/]                   now returns 1.900 72x10^8 knots.
Continue with:

Code: Select all

[RCL] 00
[f] {m->mi.}       returning 6.075 85x10^5 mi/s.
BTW, looks like 1 parsec per year is irrealisticly fast in this universe. ;)
WP43 SN00000, 34S, and 31S for obvious reasons; HP-35, 45, ..., 35S, 15CE, DM16L S/N# 00093, DM42β SN:00041
emece67

Re: 43S News

Post by emece67 »

Thanks, I got it now.
User avatar
Walter
Posts: 3070
Joined: Tue May 02, 2017 11:13 am
Location: On a mission close to DRS, Germany

Re: 43S News

Post by Walter »

You're welcome :D
WP43 SN00000, 34S, and 31S for obvious reasons; HP-35, 45, ..., 35S, 15CE, DM16L S/N# 00093, DM42β SN:00041
User avatar
ijabbott
Posts: 253
Joined: Fri Dec 15, 2017 2:34 pm
Location: GB-MAN

Re: 43S News

Post by ijabbott »

Walter wrote:
Sun Mar 18, 2018 5:18 pm
BTW, looks like 1 parsec per year is irrealisticly fast in this universe. ;)
Not surprising, since 1 parsec is about 3.26 light years! But I suppose you could perform calculations with times and distances from different reference frames to get somewhat meaningful speeds in excess of 1 parsec per year.
toml_12953
Posts: 795
Joined: Wed May 03, 2017 7:46 pm
Location: Malone, NY USA

Re: 43S News

Post by toml_12953 »

Walter wrote:
Sun Mar 18, 2018 5:18 pm

BTW, looks like 1 parsec per year is irrealisticly fast in this universe. ;)

It's not unrealistic at all. Just fold space! :)
Tom L

Some people call me inept but I'm as ept as anybody!
DM10L SN: 059/100
DM41X SN: 00023 (Beta)
DM41X SN: 00506 (Shipping)
DM42 SN: 00025 (Beta)
DM42 SN: 00221 (Shipping)
WP43 SN: 00025 (Prototype)
User avatar
Walter
Posts: 3070
Joined: Tue May 02, 2017 11:13 am
Location: On a mission close to DRS, Germany

Re: 43S News

Post by Walter »

toml_12953 wrote:
Mon Mar 19, 2018 3:42 pm
Walter wrote:
Sun Mar 18, 2018 5:18 pm
BTW, looks like 1 parsec per year is irrealisticly fast in this universe. ;)
It's not unrealistic at all. Just fold space! :)
How does a distance become smaller by folding? :?
WP43 SN00000, 34S, and 31S for obvious reasons; HP-35, 45, ..., 35S, 15CE, DM16L S/N# 00093, DM42β SN:00041
rprosperi
Posts: 1703
Joined: Mon Apr 24, 2017 7:48 pm
Location: New York

Re: 43S News

Post by rprosperi »

Walter wrote:
Mon Mar 19, 2018 5:02 pm
How does a distance become smaller by folding? :?
Read Dune. It's fairly well explained...
--bob p

DM42: β00071 & 00282, DM41X: β00071 & 00656, DM10L: 071/100
Post Reply