addressed issue #1436
addressed issue #1436

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