Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • S SEBAL
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 1
    • Issues 1
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • fogbow
  • SEBAL
  • Issues
  • #5
Closed
Open
Issue created Feb 27, 2015 by Thiago Manel@thiagoepdcOwner

Problem during the execution of the phase F2

Created by: rafaelcarv

The problem is caused when there is no H executions during the calculation of the H value for the whole image. So when the value is being calculated for each pixel, the exception below is thrown.

java.lang.ArrayIndexOutOfBoundsException: -1 at java.util.ArrayList.elementData(ArrayList.java:400) at java.util.ArrayList.get(ArrayList.java:413) at org.fogbowcloud.sebal.SEBAL.hPixelProces(SEBAL.java:340) at org.fogbowcloud.sebal.SEBAL.pixelHProcess(SEBAL.java:326) at org.fogbowcloud.sebal.wrapper.Wrapper.F2(Wrapper.java:247) at org.fogbowcloud.sebal.wrapper.Wrapper.doTask(Wrapper.java:60) at org.fogbowcloud.sebal.Main.main(Main.java:30)

This problem is also caused when the "pixel quente" chosen during the C phase has no valid values. 0.0,0.0,0.0,0.0,0.0,0.0,0.0,304.94238674624256

There is two approaches to solve this problem.

  • The first one is to investigate the phase C to detect why, sometimes, the wrong "pixel quente" is chosen.
  • The second is to do the following validation:
    • For the "pixel quente" if there is no pixel find for the ndvi main validation, chose the hottest pixel (max Ts).
    • For the "pixel frio" if there is no pixel find for the ndvi main validation, choose the pixel with the highest ndvi.
Assignee
Assign to
Time tracking