Skip to content
GitLab
Explore
Sign in
Register
Primary navigation
Search or go to…
Project
LOFAR
Manage
Activity
Members
Labels
Plan
Issues
Wiki
Jira issues
Open Jira
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Locked files
Deploy
Releases
Package Registry
Container Registry
Model registry
Operate
Environments
Terraform modules
Analyze
Value stream analytics
Contributor analytics
Repository analytics
Code review analytics
Insights
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
RadioObservatory
LOFAR
Commits
95e51445
Commit
95e51445
authored
6 years ago
by
Thomas Jürges
Browse files
Options
Downloads
Patches
Plain Diff
SW-546
: Refine the documentation of SubBandBookKeeping
parent
0c0d0910
No related branches found
Branches containing commit
No related tags found
Tags containing commit
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
RTCP/Cobalt/OutputProc/src/TBB_Dipole.h
+15
-3
15 additions, 3 deletions
RTCP/Cobalt/OutputProc/src/TBB_Dipole.h
with
15 additions
and
3 deletions
RTCP/Cobalt/OutputProc/src/TBB_Dipole.h
+
15
−
3
View file @
95e51445
...
...
@@ -117,21 +117,33 @@ namespace LOFAR
/**
* This structure is for book keeping of received sub-band data.
* I create a std::map of this with key = sub-band number in @init where
* it is read from the parset which sub-bands shall be expected and the
* map is filled accordingly. If the map does not have an entry for
* a sub-band, that sub-band is not given in the parset.
*
* When a new sub-band frame is received it is checked if the map
* @ref subBandBookKeeping contains an entry that has sub-band number
* as key. If not, the sub-band data is unexpected and the frame will
* be discarded.
*
* If the map contains an entry for the sub-band and the entry's
* @ref subBandBookKeeping.isInitialised value is false, then the entry
* will be set-up with proper data and
* @ref subBandBookKeeping.isInitialised value is false, then it is
* assumed that the just received frame is the very first frame that
* was ever sent for this sub-band and the entry will be set-up with
* proper data (setting time0 and slice0 for example) and
* @ref subBandBookKeeping.isInitialised will be set to true.
*
* Obviously the assumption above that the very first received frame for
* a sub-band is the frame that contains time0 and slice0 is breaking
* the whole concept that I do not care about the order in which frames
* for a sub-band will arrive. But hey, I have to start somewhere.
*
* From then on it is pretty simple. Every time a new frame comes in
* the data of the relevant map entry will be updated. At some point
* totalSizeInSamples == currentSizeInSamples will be true and the
* sub-band data set is complete. isComplete will be set true and any
* future frame that contains more data for this
d
ub-band will be
* future frame that contains more data for this
s
ub-band will be
* discarded.
*/
struct
SubBandBookKeeping
...
...
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