addressed issue #1472
addressed issue #1472

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