Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
  • SUNSET SUNSET
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 43
    • Issues 43
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 12
    • Merge requests 12
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Terraform modules
  • 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
  • Earth SciencesEarth Sciences
  • SUNSETSUNSET
  • Issues
  • #154
Closed
Open
Issue created Oct 25, 2024 by Nuria Pérez-Zanón@nperezMaintainer

Aggregation module returns error

Hi @vagudets ,

By chance, I got the following error:

Error in Aggregation(recipe = recipe, data = data) : 
  object 'res' not found

Because the recipe I was using for testing contain:

$Time_aggregation
$Time_aggregation$execute
[1] FALSE

Although the function Aggregation checks execute if (recipe$Analysis$Workflow$Time_aggregation$execute) { outside the condition there is the return(res).

I wonder if we need to reconsider the use of execute: yes/no in the recipe at least for this case. If it is allowed to change the option in the recipe T/F, means that I can call the module in the code, or, on the contrary, if there is no allowed option for execute in the recipe, the user should ensure if Aggregation is necessary in the code.

Cheers,

Núria

Assignee
Assign to
Time tracking