New URL for NEMO forge!   http://forge.nemo-ocean.eu

Since March 2022 along with NEMO 4.2 release, the code development moved to a self-hosted GitLab.
This present forge is now archived and remained online for history.
#1536 (change fldread to allow reading of 4 dimensions files) – NEMO

Opened 9 years ago

Closed 6 years ago

#1536 closed Task (fixed)

change fldread to allow reading of 4 dimensions files

Reported by: cbricaud Owned by: cbricaud
Priority: low Milestone: Unscheduled
Component: OCE Version: trunk
Severity: minor Keywords:
Cc:

Description


Commit History (1)

ChangesetAuthorTimeChangeLog
5399cbricaud2015-06-10T17:06:13+02:00

change fldread to allow reading of 4 dimensions files ; ticket #1536

Change History (6)

comment:1 Changed 9 years ago by cbricaud

  • Resolution set to fixed
  • Status changed from new to closed

comment:2 Changed 9 years ago by mcastril

  • Resolution fixed deleted
  • Status changed from closed to reopened

I think that this fix breaks the code.

The SIZE function gets the size of the third dimension, which normally is more than 1, so you will get always a four dimension ddims array.

The consequence in my case is that if you don't use 4 dimension temperature inputs, the model crashes in the initialization, with an error in kdimsz size, in iom_nf90.F90

1045 !! get dimensions
1046 IF ( SIZE(sd%fnow, 3) > 1 ) THEN
1047 ALLOCATE( ddims(4) )
1048 ELSE
1049 ALLOCATE( ddims(3) )
1050 ENDIF

comment:3 Changed 7 years ago by clevy

  • Owner changed from nemo to cbricaud
  • Status changed from reopened to new
  • Type changed from Enhancement to Task
  • Version changed from v3.6 to trunk

comment:4 Changed 6 years ago by nicolasmartin

  • Severity set to minor
  • Status changed from new to assigned

comment:5 Changed 6 years ago by nemo

  • Milestone set to Unscheduled

Batch modification of milestone field set to 'Unscheduled'

comment:6 Changed 6 years ago by nicolasmartin

  • Resolution set to fixed
  • Status changed from assigned to closed

I consider the bugfix as correct without further update since the ticket reopening by Miguel about 3 years ago.

If you disagree, reopen it and fix once and for all.

Note: See TracTickets for help on using tickets.