Skip to content
Snippets Groups Projects

Orog file

Merged Orog file
orog-file into master
1 unresolved thread
Merged Bianca Wentzel requested to merge orog-file into master
1 unresolved thread

Deals with one of the point mentioned here: #4 (closed)

Changes:

  • Stepwise filtering of available orog files based on given facets
  • Selection of first entry within foun dlist of available orog files

Merge request reports

Loading
Loading

Activity

Filter activity
  • Approvals
  • Assignees & reviewers
  • Comments (from bots)
  • Comments (from users)
  • Commits & branches
  • Edits
  • Labels
  • Lock status
  • Mentions
  • Merge request status
  • Tracking
pet-wrapper-api.py
139 139 name="debug",
140 140 default=False,
141 141 help="Turn on to get better detailed debug information in case you face any issue."
142 )
142 ),
  • Mostafa Hadizadeh
    Mostafa Hadizadeh @k202187 ·
    Owner

    I think this config does the job. What do u think? do u see any concern on this in long run? https://www-regiklim.dkrz.de/plugins/pet/setup/

    Suggested change
    142 ),
    142 ),
    143 SolrField(
    144 name="alti_file",
    145 facet="uri",
    146 mandatory=True,
    147 help="Altitude file.",
    148 predefined_facets={
    149 "project": ["nukleus"],
    150 "variable": ["rsds"],
    151 "time_frequency": ["1day"],
    152 },
    153 ),
  • Mostafa Hadizadeh
    Mostafa Hadizadeh @k202187 ·
    Owner

    here u go, Solr is down now with this approach :laughing:

    I don't think it's an efficient solution based on our resources

    ERROR StatusLogger Reconfiguration failed: No configuration found for '1c4af82c' at 'null' in 'null'
Aborting due to java.lang.OutOfMemoryError: Java heap space
#
# A fatal error has been detected by the Java Runtime Environment:
#
#  Internal Error (debug.cpp:362), pid=16, tid=93
#  fatal error: OutOfMemory encountered: Java heap space
#
# JRE version: OpenJDK Runtime Environment Temurin-17.0.13+11 (17.0.13+11) (build 17.0.13+11)
# Java VM: OpenJDK 64-Bit Server VM Temurin-17.0.13+11 (17.0.13+11, mixed mode, sharing, tiered, compressed oops, compressed class ptrs, g1 gc, linux-amd64)
# Core dump will be written. Default location: Core dumps may be processed with "/usr/lib/systemd/systemd-coredump %P %u %g %s %t %c %h %e" (or dumping to /opt/solr-9.6.1/server/core.16)
#
# An error report file with more information is saved as:
  • Mostafa Hadizadeh
    Mostafa Hadizadeh @k202187 ·
    Owner

    in case if it works in web, for CLI we need to figure out how user is going to provide the full path of alti file. So the suggested approach is rejected!

    I think we have to give up to the run_tool

  • Bianca Wentzel
    Bianca Wentzel @k202206 ·
    Author Owner

    So we could provide a field to provide an alti file if the user wants to specify it. Otherwise we choose one based on the submitted approach. What do you think?

  • Mostafa Hadizadeh
    Mostafa Hadizadeh @k202187 ·
    Owner

    I think there is no need to a field. Let’s keep with this approach in run_tool as is.

  • Please register or sign in to reply
  • Mostafa Hadizadeh resolved all threads

    resolved all threads

  • Mostafa Hadizadeh approved this merge request

    approved this merge request

  • Mostafa Hadizadeh
    Mostafa Hadizadeh @k202187 ·
    Owner

    LGTM!

  • Bianca Wentzel mentioned in commit 306fd426

    mentioned in commit 306fd426

  • Bianca Wentzel merged

    merged

    • Please register or sign in to reply

    Imprint | Privacy Policy