Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
NetworkedGraphicsMV3500
Manage
Activity
Members
Code
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Deploy
Releases
Container Registry
Model registry
Analyze
Contributor analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Terms and privacy
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
Savage
NetworkedGraphicsMV3500
Commits
1ed98150
Commit
1ed98150
authored
3 years ago
by
Brutzman, Don
Browse files
Options
Downloads
Patches
Plain Diff
updated README information
parent
5ba4fab3
No related branches found
No related tags found
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
examples/pduLog/README.md
+9
-4
9 additions, 4 deletions
examples/pduLog/README.md
with
9 additions
and
4 deletions
examples/pduLog/README.md
+
9
−
4
View file @
1ed98150
# PDU Log Files
This directory holds temporary files
and
may be
overwrit
te
n
at any time!
This directory holds temporary
PDU log
files
which
may be
dele
te
d
at any time!
Each time you run a DIS simulation and a PduRecorder is listening, another
log file is created.
log file is created. File names are numbered sequentially and uniquely, so that
important PDU log captures can later be copied and saved to where they are needed.
Be sure to save your work, when appropriate, by copying your log file to
[
ExamplePduCaptureLog.dislog
](
ExamplePduCaptureLog.dislog
)
shows an example log file.
Be sure to save your work, when appropriate, by copying log files of interest to
the corresponding homework or project directory (and likely renaming as well).
Note that the PDU log files are very tolerant of inline comments starting with
a # character, so you can list success/failure/TODO issues there as well.
a # character, so you can document success/failure and TODO issues there as well.
To clean out old log files, simply run
[
build.xml
](
build.xml
)
target
`clean.all.log.files`
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment