Repository: ARM-DOE/ACT

Issue:
Deprecation Warnings
Deprecation warnings from the latest build that we need to look into

`act/qc/clean.py:43
  /home/travis/build/ARM-DOE/ACT/act/qc/clean.py:43: DeprecationWarning: invalid escape sequence \_
    """
act/qc/clean.py:52
  /home/travis/build/ARM-DOE/ACT/act/qc/clean.py:52: DeprecationWarning: invalid escape sequence \("a value of 0 \(no bits set\) indicates the data has not "

act/tests/test_io.py:36
  /home/travis/build/ARM-DOE/ACT/act/tests/test_io.py:36: DeprecationWarning: invalid escape sequence \s act.tests.EXAMPLE_ANL_CSV, sep='\s+', column_names=headers)

act/tests/test_CropScape.py::test_cropType
  /home/travis/miniconda3/envs/testenv/lib/python3.7/site-packages/pyproj/crs/crs.py:280: FutureWarning: '+init=<authority>:<code>' syntax is deprecated. '<authority>:<code>' is the preferred initialization method. When making the change, be mindful of axis order changes: https://pyproj4.github.io/pyproj/stable/gotchas.html#axis-order-changes-in-proj-6
    projstring = _prepare_from_string(projparams)

act/tests/test_CropScape.py::test_cropType
  /home/travis/build/ARM-DOE/ACT/act/discovery/get_CropScape.py:80: DeprecationWarning: This function is deprecated. See: https://pyproj4.github.io/pyproj/stable/gotchas.html#upgrading-to-pyproj-2-from-pyproj-1
    x, y = pyproj.transform(inproj, outproj, lon, lat)`


Discussion:
Yeah I don't understand these warning. The code is correct. Should I wrap these parts with a with: to capture the warnings?
Since these are deprecation warnings, I do think we will have to resolve them eventually

Resolving patch:
diff --git a/act/qc/clean.py b/act/qc/clean.py
--- a/act/qc/clean.py
+++ b/act/qc/clean.py
@@ -30,10 +30,10 @@ def matched_qc_variables(self, check_arm_syntax=True):
         ----------
         check_arm_syntax : boolean
             ARM ueses a standard of starting all quality control variables
-            with "qc\_". This is a more robust method of getting the quality
-            control variables before the standard_name attribute is added.
-            If this is true will first check using attributes and will then
-            check if variable starts with "qc\_".
+            with "qc" joined with an underscore. This is a more robust method
+            of getting the quality control variables before the standard_name
+            attribute is added. If this is true will first check using
+            attributes and will then check if variable starts with "qc".
 
         Returns
         -------
@@ -49,7 +49,7 @@ def matched_qc_variables(self, check_arm_syntax=True):
                     ("This field contains bit packed integer values, where each "
                      "bit represents a QC test on the data. Non-zero bits indicate "
                      "the QC condition given in the description for those bits; "
-                     "a value of 0 \(no bits set\) indicates the data has not "
+                     "a value of 0.+ indicates the data has not "
                      "failed any QC tests."),
                     (r"This field contains bit packed values which should be "
                      r"interpreted as listed..+")


Test patch: