Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
SaQC
Manage
Activity
Members
Labels
Plan
Issues
36
Issue boards
Milestones
Wiki
Code
Merge requests
8
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Container Registry
Model registry
Operate
Environments
Monitor
Incidents
Service Desk
Analyze
Value stream analytics
Contributor analytics
CI/CD 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
rdm-software
SaQC
Commits
994dc495
Commit
994dc495
authored
5 years ago
by
Peter Lünenschloß
Browse files
Options
Downloads
Patches
Plain Diff
Update FunctionDescriptions.md
parent
d0071027
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
docs/FunctionDescriptions.md
+40
-2
40 additions, 2 deletions
docs/FunctionDescriptions.md
with
40 additions
and
2 deletions
docs/FunctionDescriptions.md
+
40
−
2
View file @
994dc495
...
@@ -710,19 +710,57 @@ Key word overview:
...
@@ -710,19 +710,57 @@ Key word overview:
if there is one available in the succeeding sampling interval. If not, BAD - flag gets assigned.
if there is one available in the succeeding sampling interval. If not, BAD - flag gets assigned.
* `
"nearest_shift"
`: every grid point gets assigned the flag in its range. ( range = +/- `
freq
`/2 ).
* `
"nearest_shift"
`: every grid point gets assigned the flag in its range. ( range = +/- `
freq
`/2 ).
* Extra flag fields like "comment", just get shifted along with the flag.
* Extra flag fields like "comment", just get shifted along with the flag.
Only inserted flags for empty intervals will signified by the set flag routine of the current flagger.
.
Only inserted flags for empty intervals will
get
signified by the set flag routine of the current flagger.
Set `
set_shift_comment
` to `
True
`, to apply setFlags signification to all flags.
Set `
set_shift_comment
` to `
True
`, to apply setFlags signification to all flags.
2. Aggregations:
2. Aggregations:
* `
"fagg"
`: all f
a
lgs in a sampling interval get aggregated with the function passed to `
agg_method
`
* `
"fagg"
`: all fl
a
gs in a sampling interval get aggregated with the function passed to `
agg_method
`
, and the result gets assigned to the last grid point.
, and the result gets assigned to the last grid point.
* `
"bagg"
`: all flags in a sampling interval get aggregated with the function passed to `
agg_method
`
* `
"bagg"
`: all flags in a sampling interval get aggregated with the function passed to `
agg_method
`
, and the result gets assigned to the next grid point.
, and the result gets assigned to the next grid point.
* `
"nearest_agg"
`: all flags in the range (+/- freq/2) of a grid point get
* `
"nearest_agg"
`: all flags in the range (+/- freq/2) of a grid point get
aggregated with the function passed to agg_method and assigned to it.
aggregated with the function passed to agg_method and assigned to it.
## `
deharmonize
`
### Signature
```
deharmonize(co_flagging)
```
### Parameters
| parameter | data type | default value | description |
| --------- | --------- | ------------- | ----------- |
| co_flagging | boolean | | |
### Description
After having calculated flags on an equidistant frequency grid, generated by
a call to a harmonization function, you may want to project
that new flags on to the original data index, or just restore the
original data shape. Then a call to `
deharmonize
` will do exactly that.
`
deharmonize
` will check for harmonization information for the variable it is
applied on (automatically generated by any call to a harmonization function of that variable)
and than:
1. Overwrite the harmonized data series with the original dataseries and its timestamps.
2. Project the calculated flags onto the original index, by inverting the
flag projection method used for harmonization, meaning, that:
* if the flags got shifted or aggregated forward, either the flag associated with the ultimatly preceeding
original timestamp, to the harmonized flag (`
co_flagging
`=`
False
`),
or all the flags, coverd by the harmonized flags preceeding sampling intervall (`
co_flagging
`=`
True
`)
get overwritten with the harmonized flag - if they are "better" than this harmonized flag.
(According to the flagging order of the current flagger.)
* if the flags got shifted or aggregated backwards, either the flag associated with the first succeeding
original timestamp, to the harmonized flag (`
co_flagging
`=`
False
`),
or all the flags, coverd by the harmonized flags succeeding sampling intervall (`
co_flagging
`=`
True
`)
get overwritten with the harmonized flag - if they are "better" than this harmonized flag.
(According to the flagging order of the current flagger.)
* if the flags got shifted or aggregated to the nearest harmonic index,
either the flag associated with the flag, nearest, to the harmonized flag (`
co_flagging
`=`
False
`),
or all the flags, covered by the harmonized flags range (`
co_flagging
`=`
True
`
)
get overwritten with the harmonized flag - if they are "better" than this harmonized flag.
(According to the flagging order of the current flagger.)
...
...
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