SegyIndex process: Use utilities::Message: rather than calls to std::cout/cerr
Type of change
-
Bug Fix -
Feature
Does this introduce a change in the core logic?
- [Yes]
Does this introduce a change in the cloud provider implementation, if so which cloud?
-
AWS -
Azure -
GCP -
IBM
Updates description?
Many cloud logging systems only catches output to std::err. To make it simpler to maintain, convert all direct output lines to using the utilities::Message::debug or utilities::Message::report class. These do the same thing, except that report will always print to std::cerr, but debug will only do it if the INDEXING_VERBOSITY or SEGYTOZGY_VERBOSITY variables are defined.