Functions to assess accuracy

[fawda123]

Using the results and dqo accuracy files, do the following:

• Input can be path or already imported data objects of both, if the former, use read_results and read_dqoaccuray to import.
• Check if all parameter values in accuracy file match those in results file, return warning
• Check if units in accuracy file match those in results file, return error
• Run accuracy checks, TBD

[fawda123]

New changes that are needed:

• [x] For Field Duplicate accuracy checks, these are filtered from entries with Field Msr/Obs and Sample-Routine that have values in the QC Reference Value field. I need to fix that and remove the Field Duplicate activity type from the acceptable checks in checkMWRresults.
• [x] For accuracy checks that use a value range, take the average of result value and QC reference value to get the right range. It currently does this with just result value (this is the part in qcMWRacc that creates 'flt')
• [x] Regarding lab spikes/instrument checks, make sure that it compares values vs percentages correctly. Is accuracy dqo column correct on import and is there an exception for value v percent comparison?
• [x] Ben will send a new results file where BDL or < value is entered for 'na' cells in lab/field blanks where the value range differs
• [x] Ben will send updated results file with E. Coli to test log and diff value ranges for accuracy checks.
• [x] Remove "media" column from qcMWRacc
• [x] For accuracy checks for lab dup, lab blank, lab spikes, and inst checks, we can create a column in the final table for "Sample ID" that pulls in entries in the Result Attribute column, if present. If not present, create blank column that can be edited by user. Ben will send updated Results file.