addressed issue #1381
addressed issue #1381

USGSDenverPychron/pychron,USGSDenverPychron/pychron,USGSDenverPychron/pychron,NMGRL/pychron,NMGRL/pychron,UManPychron/pychron,UManPychron/pychron,UManPychron/pychron,NMGRL/pychron,USGSDenverPychron/pychron,UManPychron/pychron,NMGRL/pychron