hillarymarler

After flagging replicates is developed, maybe that function can be run as part of TADA_FlagContinuousData so that replicate samples are not identified as continuous.

This issue needs to be addressed in order to finish the filter function to retain data for assessments as selected by the user (surface water, sediment, fish tissue)

I have done similar work on Illinois data in the past (finding paired T, pH, hardness, etc. sample from the same day, time and location), but only from the same...

Once we've created TADA.MonitoringLocationIdentifier (which would then be modified after site review if the decision to treat two Monitoring Locations as one?), maybe we will not need to leverage TADA_FindNearbySItes()...

There needs to be an option to substitute a default value for hardness, pH, temperature.

I've been working on this a bit. In the case of hardness, there are multiple characteristic names that correspond to hardness. In the current draft, users can rank the characteristic...

I have a working draft of a pairing function in the demo_impairment_functions branch (https://github.com/USEPA/EPATADA/blob/demo_impairment_functions/R/Module3.R). Relevant code begins at line 282 and includes two functions, TADA_CreatePairRef and TADA_PairForCriteriaCalc. I have not...

I moved this function to its own branch/BR (it is no longer in the demo_impairment_functions branch).

How should we handle situations where no bottom depth measures are provided?

We may need to update TADA_RetainRequired function depending on which depth columns we'd like to retain for plotting/analysis in the Shiny app