addressed issue #1273
addressed issue #1273

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