43S News
Re: 43S News
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.
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.
Re: 43S News
(emphasis added)
And about units, please allow me quoting the draft manual:
HTH, else continue asking.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.
DM42 SN: 00041  Follower of Platon.
HP35, HP45, ..., HP50, WP 34S, WP 31S, DM16L
HP35, HP45, ..., HP50, WP 34S, WP 31S, DM16L
Re: 43S News
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:Walter wrote: ↑Sat Mar 17, 2018 5:20 pmnd about units, please allow me quoting the draft manual:HTH, else continue asking.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.
 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
Re: 43S News
Let's see what's provided already solving your problems  {...} embraces softkeys:emece67 wrote: ↑Sat Mar 17, 2018 10:42 pmUnfortunately, 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:Walter wrote: ↑Sat Mar 17, 2018 5:20 pmAnd about units, please allow me quoting the draft manual:HTH, else continue asking.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.
 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
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
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.
Code: Select all
[RCL] 00
[f] {m>mi.} returning 6.075 85x10^5 mi/s.
DM42 SN: 00041  Follower of Platon.
HP35, HP45, ..., HP50, WP 34S, WP 31S, DM16L
HP35, HP45, ..., HP50, WP 34S, WP 31S, DM16L
Re: 43S News
You're welcome
DM42 SN: 00041  Follower of Platon.
HP35, HP45, ..., HP50, WP 34S, WP 31S, DM16L
HP35, HP45, ..., HP50, WP 34S, WP 31S, DM16L
Re: 43S News
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.

 Posts: 584
 Joined: Wed May 03, 2017 5:46 pm
 Location: Malone, NY USA
Re: 43S News
It's not unrealistic at all. Just fold space!
Tom L
DM10L SN: 059/100
DM41X SN: 00023 (Beta)
DM42 SN: 00025 (Beta)
SN: 00221 (Shipping)
DM10L SN: 059/100
DM41X SN: 00023 (Beta)
DM42 SN: 00025 (Beta)
SN: 00221 (Shipping)
Re: 43S News
How does a distance become smaller by folding?
DM42 SN: 00041  Follower of Platon.
HP35, HP45, ..., HP50, WP 34S, WP 31S, DM16L
HP35, HP45, ..., HP50, WP 34S, WP 31S, DM16L