addressed issue #1511
addressed issue #1511

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