Communities

Writing
Writing
Codidact Meta
Codidact Meta
The Great Outdoors
The Great Outdoors
Photography & Video
Photography & Video
Scientific Speculation
Scientific Speculation
Cooking
Cooking
Electrical Engineering
Electrical Engineering
Judaism
Judaism
Languages & Linguistics
Languages & Linguistics
Software Development
Software Development
Mathematics
Mathematics
Christianity
Christianity
Code Golf
Code Golf
Music
Music
Physics
Physics
Linux Systems
Linux Systems
Power Users
Power Users
Tabletop RPGs
Tabletop RPGs
Community Proposals
Community Proposals
tag:snake search within a tag
answers:0 unanswered questions
user:xxxx search by author id
score:0.5 posts with 0.5+ score
"snake oil" exact phrase
votes:4 posts with 4+ votes
created:<1w created < 1 week ago
post_type:xxxx type of post
Search help
Notifications
Mark all as read See all your notifications »
Q&A

How would floating point numbers be affecting space and time travel in future?

+0
−0

Each technology, that is evolving, begins with simple piece of programming code that starts with variables of certain data types. It is interesting to note that many calculative and computing technologies including system clocks have "float" (and similar other) data types which can store floating point numbers. There are many evidences already which depicts how human errors in judgement and prediction have created floating point errors and ended up in a chaotic disaster.

Just to illustrate a few of them to support my question:

February 25,1991: 28 American soldiers killed due to floating point error!!

The time in tenths of second as measured by the system's internal clock was multiplied by 1/10 to produce the time in seconds. This calculation was performed using a 24 bit fixed point register. In particular, the value 1/10, which has a non-terminating binary expansion, was chopped at 24 bits after the radix point. The small chopping error, when multiplied by the large number giving the time in tenths of a second, lead to a significant error. (Source)

June 4, 1996: Blast in an unmanned spaceship during launch

The rocket was on its first voyage, after a decade of development costing dollar 7 billion. It turned out that the cause of the failure was a software error in the inertial reference system. Specifically a 64 bit floating point number relating to the horizontal velocity of the rocket with respect to the platform was converted to a 16 bit signed integer. The number was larger than 32,768, the largest integer storeable in a 16 bit signed integer, and thus the conversion failed. (Source)

There are lots of examples out there where, 10th or even 100th floating point multiplied small chain of errors to huge disasters.

While in future, when space and time travel is considered a definite possibility, How should such unpredictable errors be handled? How would programming and development of such long travels be done specifically with floating point values?

Bonus: how would the cause of any such failure would be recognized or investigated if it occurred during space and time travel?

Edit: Don't Consider Unpredictable literally. It was just a hyperbole annotation used. I simply just meant "Hard to predict"

History
Why does this post require attention from curators or moderators?
You might want to add some details to your flag.
Why should this post be closed?

This post was sourced from https://worldbuilding.stackexchange.com/q/65897. It is licensed under CC BY-SA 3.0.

0 comment threads

0 answers

Sign up to answer this question »