Opened 4 years ago

Last modified 4 years ago

#122 new Enhancement

Improve MQUASILAG option

Reported by: pesei Owned by: somebody
Priority: critical Milestone: FLEXPART 9.2
Component: FP physics/numerics Version: FLEXPART 9.0.2
Keywords: Cc:

Description

Quasi-Lagrangian output, i.e. particle IDs and positions, is not well implemented yet.

In readcommand.f90:

  ! For quasilag output for each release is forbidden
  ! For quasilag backward is forbidden

In partoutput_short.f90:

  ! Convert positions to integer*2 variables (from -32768 to 32767)
  ! Do this only for region of main interest, i.e. extended North Atlantic region,
  ! and for the tracer of interest, i.e. the North American one
  !*****************************************************************************

      if (xlon.gt.180.) xlon=xlon-360.
      if (xlon.lt.-180.) xlon=xlon+360.

      numshortall=numshortall+1
      if ((xlon.gt.-140).and.(xlon.lt.60).and.(ylat.gt.10).and. &
           (xmass1(i,1).gt.0.)) then
        numshortout=numshortout+1
        idump(1,numshortout)=nint(xlon*180.)
        idump(2,numshortout)=nint(ylat*360.)
        zlim=min(ztra1(i)+topo,32766.)
        idump(3,numshortout)=nint(zlim)
        i4dump(numshortout)=npoint(i)
      endif

    endif
  end do

I don't see the reasons for these limitations, and in any case, they are not desirable (cf. recent FLEXPART discussion list posting, Subject: Particle tracking).

Change History (1)

comment:1 Changed 4 years ago by pesei

      if ((mquasilag.eq.1).and.(itime.eq.(loutstart+loutend)/2)) &
         call partoutput_short(itime)    
         ! dump particle positions in extremely compressed format

Why is quasilag output in the middleof the output interval?

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