Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • S S1Tiling
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 37
    • Issues 37
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 4
    • Merge requests 4
  • 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
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • s1-tiling
  • S1Tiling
  • Issues
  • #93
Closed
Open
Issue created Aug 18, 2021 by Thierry Koleck@kolecktMaintainer

All images are not processed when running once

Working on large scale (hundred of tiles on one year), I remarked that the second run of s1tiling (without changing parameters) find again new images to process. It seems that some images are missing on the first run.

May be it is a problem with the data provider (PEPS in my case).

So I need to run s1tiling several time to be sure that all data are processed.

Anyway, I am not sure that the following situation is correctly managed. In the case of two images to be concatenated, if the second image is missing on the first run, are we sure that the second run will find the second image and do the concatenation ?

As the problem appends randomly, it is not easy to find a case.

May be this problem on the second run can be solve with issue #69 (closed)

Assignee
Assign to
Time tracking