Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in
Toggle navigation
C
codes
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
38
Issues
38
List
Boards
Labels
Milestones
Merge Requests
8
Merge Requests
8
Analytics
Analytics
Repository
Value Stream
Wiki
Wiki
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Commits
Issue Boards
Open sidebar
codes
codes
Commits
ec4c6370
Commit
ec4c6370
authored
Mar 20, 2014
by
Jonathan Jenkins
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
floating point best practices
parent
2e7b25cc
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
8 additions
and
0 deletions
+8
-0
doc/codes-best-practices.tex
doc/codes-best-practices.tex
+8
-0
No files found.
doc/codes-best-practices.tex
View file @
ec4c6370
...
...
@@ -419,6 +419,14 @@ reverse handler only needs to reverse as single event, in order)
\item
how to handle queues
\end{itemize}
\subsection
{
Working with floating-point data
}
Floating point variables are particularly tricky to use in optimistic
simulations, as rounding errors prevent rolling back to a consistent state by
merely performing the inverse operations (e.g.,
$
a
+
b
-
b
\neq
a
$
). Hence, it is
instead preferable to simply store the local floating-point state in the event
structure and perform assignment on rollback.
\subsection
{
How to complete a simulation
}
TODO: fill this in. Most core ROSS examples are design to intentionally hit
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment