addressed issue #1223
addressed issue #1223

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