addressed issue #1287
addressed issue #1287

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