Opened 4 years ago

Last modified 4 years ago

#124 accepted Enhancement

Suggest easing of restriction on number of releases in readpartpositions.f90

Reported by: donaldjmorton Owned by: pesei
Priority: minor Milestone: FLEXPART 9.2
Component: FP other Version: FLEXPART 9.0.2
Keywords: Cc:

Description

Given another very bad fire year in Alaska, I am running FLEXPART operationally, warm starting from one run to the next. Because of the dynamic nature of releases (new fires, some fires suppressed), it is normal that the number of releases saved from a previous run to warm start a new run will not be the same as the number of releases in the new run.

In readpartpositions.f90, I have found it necessary to comment out the following code (in the vicinity of Line 78) in order to allow for different number of releases from one run to the next.

  read(unitpartin) numpointin
!!!!!!!!!!!!!! MODIFICATION DJM  2015-06-20 - comment out the
!!!!!!!!!!!!!! following restriction
! if (numpointin.ne.numpoint) goto 995

I understand there may be very good reason to have this restriction, but at least in my case it gets in the way.

Change History (1)

comment:1 Changed 4 years ago by pesei

  • Milestone set to FLEXPART 9.2
  • Owner changed from somebody to pesei
  • Status changed from new to accepted
  • Type changed from Defect to Enhancement

If we accept this in the main Fp code, I would at least output a very visible WARNING.

Note: See TracTickets for help on using tickets.
hosted by ZAMG