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
e83023c1
Commit
e83023c1
authored
4 years ago
by
Bert Palm
🎇
Browse files
Options
Downloads
Patches
Plain Diff
Apply 6 suggestion(s) to 1 file(s)
parent
fe73bbe2
No related branches found
Branches containing commit
No related tags found
Tags containing commit
1 merge request
!218
Flags
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
saqc/flagger/history.py
+6
-6
6 additions, 6 deletions
saqc/flagger/history.py
with
6 additions
and
6 deletions
saqc/flagger/history.py
+
6
−
6
View file @
e83023c1
...
...
@@ -14,7 +14,7 @@ class History:
``append`` is called a new column is appended to the FH. The column
names are increasing integers starting with 0. After initialisation
the FH is empty and has no columns at all. If an initial `UNFLAGGED`-
column is desired, it must created manually, or passed via the ``hist``
column is desired, it must
be
created manually, or passed via the ``hist``
parameter. The same way a new FH can be created from an existing one.
To get the worst flags (highest value) that are currently stored in
...
...
@@ -22,11 +22,11 @@ class History:
the worst flag per row.
To counteract the problem, that one may want to force a better flag
value than the current
ly
worst, ``append`` provide a ``force`` keyword.
value than the current worst, ``append`` provide a ``force`` keyword.
Internal we need to store the force information in an additional mask.
For more details and a detailed discussion, why this is needed, how this
works and possible other implementations, see #G
H
143 [1].
works and possible other implementations, see #G
L
143 [1].
[1] https://git.ufz.de/rdm-software/saqc/-/issues/143
...
...
@@ -61,7 +61,7 @@ class History:
mask
=
pd
.
DataFrame
()
elif
hist
is
None
and
mask
is
not
None
:
raise
ValueError
(
"
Cannot take
'
mask
'
with
no
'
hist
'"
)
raise
ValueError
(
"
Cannot take
'
mask
'
with
out
'
hist
'"
)
elif
hist
is
not
None
and
mask
is
None
:
hist
=
self
.
_validate_hist
(
hist
)
...
...
@@ -87,7 +87,7 @@ class History:
Notes
-----
The index should always be equal to the flags series,
th
is is
FH is associated with. If this is messed up
th
e
FH is associated with. If this is messed up
something went wrong in saqc internals or in a user-
defined test.
...
...
@@ -223,7 +223,7 @@ class History:
-----
The new column number (column name) will be the lowest of
the squeezed. This ensure that the column numbers are always
monotonic increasing.
monotonic
ally
increasing.
Bear in mind, this works inplace, if a copy is needed, call ``copy`` before.
...
...
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