addressed issue #1054
addressed issue #1054

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