Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
metro
metro
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 9
    • Issues 9
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 0
    • Merge Requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Analytics
    • Analytics
    • CI/CD
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • METRo projects
  • metrometro
  • Issues
  • #1

Closed
Open
Created Jun 16, 2017 by Miguel Tremblay@MiguelTremblayMaintainer

METRo immediately diverges from obs

Original submission by Seth Linden on Gna! on Mon 05 Apr 2010 09:27:17 PM UTC

I've been looking into a road-T fcst run-to-run consistency issue and it comes down to the fact that during the day (especially mid-morning), METRo quickly diverges from the road-T observations provided in the obs-history. This causes the road-T forecast time-series to get increasingly warmer and warmer from run to run. In the example I have provided here:

For the 18z run: the obs-history value valid at 18z is 41.07 the first road-T fcst values valid at 18:20z is 45.77 the road-T fcst value at 19z is 48.86

I does not seem realistic that the road-T jumps 4.7 degC in 20 minutes.

Any insight would be greatly appreciated.

I have attached the example input and output file(s).

Thanks,
Seth Linden

obs.0.99.xml

met.0.99.xml

roadcast.000.99.xml

station.0.99.xml

Assignee
Assign to
METRo 4
Milestone
METRo 4 (Past due)
Assign milestone
Time tracking
None
Due date
None