Closed Ovec8hkin closed 5 years ago
@falkamelung Which of the above options would you like to see implemented. The monolithic log file is more standard within the software development industry but can be more difficult to filter through and find errors (@2gotgrossman or @Ovec8hkin can write something to help with that). Having a separate log in each project directory is a cleaner interface, but the logs are no longer centralized, which makes finding a bit more time consuming.
Not sure I understand. I thought we talked about it. When it is called from run_operations it should end up in the OPERATIONS/LOG. When it is not called from run_operations it should be in the project_directory and when a run is complete the log file will be moved into the OPERATIONS/LOG directory. I have no problem to have multiple log files instead of a monolithic one. I guess once we are fully in operations we could switch to a monolithic one but I don't see an advantage compared to multiple smaller ones. Actually, the multiple smaller onces are easier to handle as files older than, say, 6 month coule be easily removed.
Falk Amelung Professor Department of Marine Geosciences Rosenstiel School of Marine and Atmospheric Sciences University of Miami 4600 Rickenbacker Causeway Miami, FL 33149 USA Tel: 305 421 4949 E-mail: famelung@rsmas.miami.edumailto:famelung@rsmas.miami.edu Web: http://insar.rsmas.miami.edu InSAR data: http://insarmaps.miami.edu
On Mar 6, 2019, at 8:33 AM, Joshua Zahner notifications@github.com<mailto:notifications@github.com> wrote:
@falkamelunghttps://nam01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Ffalkamelung&data=02%7C01%7Cfamelung%40rsmas.miami.edu%7C7dc01d1fb0db4b78278e08d6a23851d6%7C2a144b72f23942d48c0e6f0f17c48e33%7C0%7C0%7C636874760106424623&sdata=4aNfQmMeyiV%2FRJEFwgjodHyu85HpvxuX6cqKvWWniRI%3D&reserved=0 Which of the above options would you like to see implemented. The monolithic log file is more standard within the software development industry but can be more difficult to filter through and find errors (@2gotgrossmanhttps://nam01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2F2gotgrossman&data=02%7C01%7Cfamelung%40rsmas.miami.edu%7C7dc01d1fb0db4b78278e08d6a23851d6%7C2a144b72f23942d48c0e6f0f17c48e33%7C0%7C0%7C636874760106434632&sdata=rUqGWpQSynzELfz2zLoghMXoi3GqSjM9wkOa%2Frrkgf4%3D&reserved=0 or @Ovec8hkinhttps://nam01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FOvec8hkin&data=02%7C01%7Cfamelung%40rsmas.miami.edu%7C7dc01d1fb0db4b78278e08d6a23851d6%7C2a144b72f23942d48c0e6f0f17c48e33%7C0%7C0%7C636874760106434632&sdata=4W99%2BhWz5IFaf5VgJLY8KNtrB0Jv5g2C7viJJqO2d%2Fs%3D&reserved=0 can write something to help with that). Having a separate log in each project directory is a cleaner interface, but the logs are no longer centralized, which makes finding a bit more time consuming.
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHubhttps://nam01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fgeodesymiami%2Frsmas_isce%2Fissues%2F88%23issuecomment-470108346&data=02%7C01%7Cfamelung%40rsmas.miami.edu%7C7dc01d1fb0db4b78278e08d6a23851d6%7C2a144b72f23942d48c0e6f0f17c48e33%7C0%7C0%7C636874760106444646&sdata=AHM5K8Az%2FFKOpG603aeMo6NQxBRXorJnTd5V8kHacfg%3D&reserved=0, or mute the threadhttps://nam01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAKpT3EHGRyM0fXVkdHg2fn1EsvCFkacKks5vT8OogaJpZM4bg4my&data=02%7C01%7Cfamelung%40rsmas.miami.edu%7C7dc01d1fb0db4b78278e08d6a23851d6%7C2a144b72f23942d48c0e6f0f17c48e33%7C0%7C0%7C636874760106444646&sdata=cFW6kFnD13zpm%2FzJwIgL6rD2V%2BLJUXk%2BPU6AO2tUD8g%3D&reserved=0.
Output log files from
run_operations.py
to a centralized directory for easy access and review. Ideally, this should take the form of a monolithic master log file (run_operations.log
) in the $OPERATIONS/LOGS directory, but could also be written directly to the project workspace (ie./projects/scratch/insarlab/jaz101/KinneretSenDT21/run_operations.log
)