Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

"minimum 1.0 sapling DBH" popping-up frequently #122

Closed
abrolis opened this issue Apr 25, 2019 · 4 comments
Closed

"minimum 1.0 sapling DBH" popping-up frequently #122

abrolis opened this issue Apr 25, 2019 · 4 comments
Assignees
Labels
bug Functionality does not work as designed field season need Issue needs to be resolved for upcoming field season fix Resolve this issue P2 - High Priority 2 - Issue is a high priority to resolve

Comments

@abrolis
Copy link

abrolis commented Apr 25, 2019

Joe says "It happens after inputting the DBH and then it usually happens a second time when you go through the VCF options. I think it still happens after you click the double check the DBH box."

@abrolis abrolis added fix Resolve this issue bug Functionality does not work as designed P2 - High Priority 2 - Issue is a high priority to resolve field season need Issue needs to be resolved for upcoming field season labels Apr 25, 2019
@lizmatthews03
Copy link

To clarify, this pop-up comes up for every sapling. If we can't fix it, let's disable it.

@blcampbell blcampbell added this to the 2019 Pre-Season Updates milestone May 6, 2019
@abrolis
Copy link
Author

abrolis commented Nov 6, 2019

Ideally the sapling DBH pop-up would be there so that we know we actually did double check the DBH of a sapling that grew or shrank too much.

Nick says "The issue is the DBH warning pop-up often pops up when there is no issue, saying “saplings must be at least 1 cm” after we had entered a DBH that was far greater than 1 cm. We dismissed the sapling DBH popup all season because it wasn’t functioning properly and checked off the double check automatically. But there were saplings that may have needed a double check that were flagged in QA/QC (see example below).

Example: CATO-0037 has a sapling (22244) with a DBH of 2.4 cm on a single stem in 2015 sampling and a DBH of 8.4 cm on three stems (7, 1.8, 3.9) in 2019. "

@blcampbell
Copy link
Contributor

Popup for every sapling should be resolved, however in some instances the stems DBH value doesn't update before the check resulting in an invalid DBH popup.

image

image

@blcampbell
Copy link
Contributor

Added a function (check) that tests for Equiv DBH before the DBH check that triggers popups.

Result
Even though the subform doesn't update L/D to 8.39 (example above) before the DBH check the new function retrieves the actual value and does not allow the check to proceed unless the value is < 1.

Important
Need test cases to check that this fix still allows the popup to proceed when it should - including tests in the field.

blcampbell pushed a commit that referenced this issue Apr 21, 2021
Version 9.8.0.9005
2021 Pre-Season Updates
Incremental release addresses the following…

**Export issues**
Closes #9(Prevent RFS tag exports)
Closes #16(Browse data not exported for herbaceous species)
Closes #18(DBH/basal area not exported for dead trees)
Closes #76(Saplings w/o habit excluded)
Closes #77(Include DBH double-checked? w/ @ DBH record)
Closes #80(Export DBH double checked In tree/sapling CSVs)
Closes #83(Add comments)
Closes #90(Add state/county to plots export)
Closes #105(Trees w/o azimuth/distance not exported)
Closes #107(Tree/sapling vigor not exported)
Closes #138(CWD exports incorrectly)
Closes #201 (Export function does not work)
Closes #216(Change UnitCode to Unit_Code)
Closes #217(Duplicate records for synonyms)
Closes #220(Add and expose plant species export field)
Closes #221(Add tlu_Plants Export field)
Closes #222(Export species lists)

**Event Report issues**
Closes #3 (Identify trees surpassing threshold)
Closes #20(Equivalent DBH should display)
Closes #63(Report doesn't open from gateway form)
Closes #64(No Tree Conditions red bar appears on all living trees w/o tree conditions selected)
Closes #65(Sapling foliar conditions don't show)
Closes #72(Sapling foliar issues not showing)
Closes #75(Missing tree/sapling/shrub ID doesn't highlight)
Fixes #112(Number appears at top)
Fixes #113(Not showing trees)
Closes #157(Sapling VCF checkboxes not showing)
Closes #158(Missing sapling DBHs not highlighted)
Closes #174(Monster saplings because of dead standing DBH)
Closes #178(Remove RIO from unsampled tags & event report)
Closes #184(Highlight herbaceous species cover < 0%)
Closes #197(Prior DBH's not correct)
Closes #294(Add stem prior DBHs)

**Import Issues**
Fixes #127(Quadrat data doesn't import)
Closes #139(Only 1 event imports per day)
Fixes #140(Secondary events from pseudoevents not imported)
Fixes #199 (Issue w/ importing tables from field data)

**Species Issues**
Closes #99(Add Berberis bealei to plants)
Closes #219(Add Parthenocissus tricuspidata)


**Data Issues**
Closes #66(Update tag status for all dead fall trees)
Closes #71(Delete MONO-0026 tag 99999)
Fixes #74(Move 2 trees from PRWI-0082 to PRWI-0028)
Closes #95(Retag 3593 to 25278)
Closes #96(Issues w/ tag 3250)
Fixes #89(Extra event)
Closes #223(Synonyms - change to new TSN_Accepted)
Closes #224(Synonyms - split out distinct species)
Closes #225(Synonyms - add new species as new default TSN_Accepted)

**General issues**
Closes #12(Add new plot data to locations table)
Closes #21(Deleted issue)
Closes #44(Species pad allow double click selection)
Closes #68(Vigor data field highlighted after crown class entry)
Closes #69(Target herb percent cover autofills to 0 after taxon entry)
Closes #70(Add quick comment "old primary branch broken")
Closes #78(Display all vs active tags)
Closes #85(Handle pseudo-events)
Closes #87(Sort tag history by date)
Closes #88(Add change log functionality to browse tag form)
Closes #91(Sapling tag status doesn’t update)
Closes #92(Pseudoevent - conversion to actual event)
Closes #103(Automatically update "habit" for saplings/shrubs based on species ID)
Closes #106(Preserve pseudo-event date)
Closes #111(Add tree/sapling/shrub condition for stress related to vines)
Closes #114(Tags not shifting to sampled on events form)
Closes #115(DBH double checked background remains)
Closes #120(RIO tags show at top of dropdown)
Closes #121(Targeted herbs % autofills to 0 w/ species selection)
Closes #122(Minimum 1.0 sapling DBH frequenlly pops up)
Closes #123(Add Show/Hide for trees we won't sample in unsampled tag dropdown)
Closes #124(Add buttons to browse plants/tags from events form)
Fixes #126(Lookup code for spotted lanternfly missing)
Closes #128(Sampled tag dropdown missing tree/sapling status)
Closes #136(Highlight when tag RFS flag set)
Closes #145(Post-Season review - RIO tags)
Closes #146(Event date(s) need to be updated)
Closes #156(Drop-down comments for change log not populating for azimuth/distance)
Closes #166(Shrinking DBHs not flagged)
Closes #171(64-bit conversion)
Closes #172(Integrate framework modules)
Closes #176(Herbaceous species w/o % cover or browse)
Closes #196(Cannot input multiple DBH measurements for multi-stemmed sapling)
Closes #198 (Unexpected popup when inputting living status for saplings)
Fixes #200 (Cannot create Db backup)
Fixes #202 (PriorDBH Incorrect)
Closes #203 (Add PriorDBH to tree/sapling Forms)
Fixes #205 (Advanced Data Summary - Event Summary report displays overlain text)
Fixes #207(New Event triggers null error for DBH)
Fixes #208(Unable to create new event)

Partially addresses (these are not fully exposed/implemented)
#100 (Add taxonomic reference adjustments)
#181 (Event Report - tree/sapling vine loss)
#186 (Allow event date changes)
#187 (Add measurement data flags set/edit/delete)
#188 (Add SOP version tracking)
#189(Add data flag utilities)
#192(Add event DPL utilities)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Functionality does not work as designed field season need Issue needs to be resolved for upcoming field season fix Resolve this issue P2 - High Priority 2 - Issue is a high priority to resolve
Projects
None yet
Development

No branches or pull requests

3 participants