Logging in ESD Operator

[esteban.aguilera]

I’ve noticed that the Enhanced Spectral Diversity (ESD) operator prints out many INFO lines.

For example:

INFO: org.esa.s1tbx.sentinel1.gpf.SpectralDiversityOp: RangeShiftOp: burst = 3, azimuth offset = 0.0
INFO: org.esa.s1tbx.sentinel1.gpf.SpectralDiversityOp: RangeShiftOp: burst = 3, range offset = 0.0
INFO: org.esa.s1tbx.sentinel1.gpf.SpectralDiversityOp: RangeShiftOp: burst = 2, azimuth offset = 0.0
INFO: org.esa.s1tbx.sentinel1.gpf.SpectralDiversityOp: RangeShiftOp: burst = 2, range offset = 0.0
INFO: org.esa.s1tbx.sentinel1.gpf.SpectralDiversityOp: RangeShiftOp: burst = 1, azimuth offset = 0.0
INFO: org.esa.s1tbx.sentinel1.gpf.SpectralDiversityOp: RangeShiftOp: burst = 1, range offset = 0.0
INFO: org.esa.s1tbx.sentinel1.gpf.SpectralDiversityOp: RangeShiftOp: burst = 4, azimuth offset = 0.0
INFO: org.esa.s1tbx.sentinel1.gpf.SpectralDiversityOp: RangeShiftOp: burst = 4, range offset = 0.0
INFO: org.esa.s1tbx.sentinel1.gpf.SpectralDiversityOp: RangeShiftOp: burst = 6, azimuth offset = 0.0
INFO: org.esa.s1tbx.sentinel1.gpf.SpectralDiversityOp: RangeShiftOp: burst = 6, range offset = 0.0
INFO: org.esa.s1tbx.sentinel1.gpf.SpectralDiversityOp: RangeShiftOp: burst = 7, azimuth offset = 0.0
INFO: org.esa.s1tbx.sentinel1.gpf.SpectralDiversityOp: RangeShiftOp: burst = 7, range offset = 0.0
INFO: org.esa.s1tbx.sentinel1.gpf.SpectralDiversityOp: RangeShiftOp: burst = 5, azimuth offset = 0.0
INFO: org.esa.s1tbx.sentinel1.gpf.SpectralDiversityOp: RangeShiftOp: burst = 5, range offset = 0.0
INFO: org.esa.s1tbx.sentinel1.gpf.SpectralDiversityOp: RangeShiftOp: burst = 0, azimuth offset = 0.0
INFO: org.esa.s1tbx.sentinel1.gpf.SpectralDiversityOp: RangeShiftOp: burst = 0, range offset = 0.25
INFO: org.esa.s1tbx.sentinel1.gpf.SpectralDiversityOp: RangeShiftOp: whole image azimuth offset = 0.0
INFO: org.esa.s1tbx.sentinel1.gpf.SpectralDiversityOp: RangeShiftOp: whole image range offset = 0.03125
INFO: org.esa.s1tbx.sentinel1.gpf.SpectralDiversityOp: estimateAzimuthOffset numOverlaps = 7
INFO: org.esa.s1tbx.sentinel1.gpf.SpectralDiversityOp$2: forwardRectangle = java.awt.Rectangle[x=10000,y=1343,width=512,height=149]
INFO: org.esa.s1tbx.sentinel1.gpf.SpectralDiversityOp$2: backwardRectangle = java.awt.Rectangle[x=10000,y=1492,width=512,height=149]
INFO: org.esa.s1tbx.sentinel1.gpf.SpectralDiversityOp$2: forwardRectangle = java.awt.Rectangle[x=10000,y=2836,width=512,height=148]
INFO: org.esa.s1tbx.sentinel1.gpf.SpectralDiversityOp$2: backwardRectangle = java.awt.Rectangle[x=10000,y=2984,width=512,height=148]
INFO: org.esa.s1tbx.sentinel1.gpf.SpectralDiversityOp$2: forwardRectangle = java.awt.Rectangle[x=10000,y=4327,width=512,height=149]
INFO: org.esa.s1tbx.sentinel1.gpf.SpectralDiversityOp$2: backwardRectangle = java.awt.Rectangle[x=10000,y=4476,width=512,height=149]
INFO: org.esa.s1tbx.sentinel1.gpf.SpectralDiversityOp$2: forwardRectangle = java.awt.Rectangle[x=10000,y=5816,width=512,height=152]
INFO: org.esa.s1tbx.sentinel1.gpf.SpectralDiversityOp$2: backwardRectangle = java.awt.Rectangle[x=10000,y=5968,width=512,height=152]
INFO: org.esa.s1tbx.sentinel1.gpf.SpectralDiversityOp$2: forwardRectangle = java.awt.Rectangle[x=10000,y=7314,width=512,height=146]
INFO: org.esa.s1tbx.sentinel1.gpf.SpectralDiversityOp$2: backwardRectangle = java.awt.Rectangle[x=10000,y=7460,width=512,height=146]
INFO: org.esa.s1tbx.sentinel1.gpf.SpectralDiversityOp$2: forwardRectangle = java.awt.Rectangle[x=10000,y=8802,width=512,height=150]
INFO: org.esa.s1tbx.sentinel1.gpf.SpectralDiversityOp$2: backwardRectangle = java.awt.Rectangle[x=10000,y=8952,width=512,height=150]
INFO: org.esa.s1tbx.sentinel1.gpf.SpectralDiversityOp$2: forwardRectangle = java.awt.Rectangle[x=10000,y=10295,width=512,height=149]
INFO: org.esa.s1tbx.sentinel1.gpf.SpectralDiversityOp$2: backwardRectangle = java.awt.Rectangle[x=10000,y=10444,width=512,height=149]
INFO: org.esa.s1tbx.sentinel1.gpf.SpectralDiversityOp$2: azOffset = -0.001390231491998066
INFO: org.esa.s1tbx.sentinel1.gpf.SpectralDiversityOp$2: azOffset = 8.180151612069521E-4
INFO: org.esa.s1tbx.sentinel1.gpf.SpectralDiversityOp$2: azOffset = 1.174227500043344E-4
INFO: org.esa.s1tbx.sentinel1.gpf.SpectralDiversityOp$2: azOffset = 0.0011403076794674213
INFO: org.esa.s1tbx.sentinel1.gpf.SpectralDiversityOp$2: azOffset = 0.0037891785026124155
INFO: org.esa.s1tbx.sentinel1.gpf.SpectralDiversityOp$2: azOffset = -6.544997475422439E-4
INFO: org.esa.s1tbx.sentinel1.gpf.SpectralDiversityOp$2: azOffset = 4.6443936906618113E-4
INFO: org.esa.s1tbx.sentinel1.gpf.SpectralDiversityOp: AzimuthShiftOp: overlap area = 4, azimuth offset = -0.001390231491998066
INFO: org.esa.s1tbx.sentinel1.gpf.SpectralDiversityOp: AzimuthShiftOp: overlap area = 3, azimuth offset = 8.180151612069521E-4
INFO: org.esa.s1tbx.sentinel1.gpf.SpectralDiversityOp: AzimuthShiftOp: overlap area = 5, azimuth offset = 1.174227500043344E-4
INFO: org.esa.s1tbx.sentinel1.gpf.SpectralDiversityOp: AzimuthShiftOp: overlap area = 1, azimuth offset = 0.0011403076794674213
INFO: org.esa.s1tbx.sentinel1.gpf.SpectralDiversityOp: AzimuthShiftOp: overlap area = 0, azimuth offset = 0.0037891785026124155
INFO: org.esa.s1tbx.sentinel1.gpf.SpectralDiversityOp: AzimuthShiftOp: overlap area = 2, azimuth offset = -6.544997475422439E-4
INFO: org.esa.s1tbx.sentinel1.gpf.SpectralDiversityOp: AzimuthShiftOp: overlap area = 6, azimuth offset = 4.6443936906618113E-4
INFO: org.esa.s1tbx.sentinel1.gpf.SpectralDiversityOp: AzimuthShiftOp: whole image azimuth offset = 6.12090317545285E-4

Do you think this could be switched off? or maybe just stored in the output .dim?

I’m using yesterday’s master branch (May 17).

[SvH]

Hi Esteban,

your question might already be partially aswered in:

Suppress output by Cross-CorrelationOp when run in GPT

Hi developers, we are running (many) graph files via the GPT in an automated fashion (orchestrated by an external tool). We currently experience the issue that GRAPH's, containing a Cross-Correlation operator, generate so much output to the stdout, that our logging framework gets overloaded and chokes on it. Is there a way that we can control/reduce the amount of msg this operator produces? It seems that only this specific operator generates so many msg.... Thanks alot in advance! Sven.

At least a temporary workaround is mentioned.

Best regards,
Sven.

[marpet]

As Sven mentioned already, if you add the Java VM option “-Dsnap.log.level=WARNING” to the gpt.vmoptions only errors and warnings will be shown if the logger is correctly used by the operator.
However, I think the level for those messages can be probably changed to DEBUG.
Can this be done @lveci?

[esteban.aguilera]

Thanks, that helps already!