Skip to content
Snippets Groups Projects
Select Git revision
  • master
  • development
  • v10.4.1
  • lcm_nudge
  • m_lcm
  • flexpart_lcm
  • fix_GFS
  • optimise
  • fix_GFS_23
  • feature_gfs_fix
  • wetdepo_bugfix
  • feature/newWetDepo
  • tests
  • christine
  • split_mods
  • openmp
  • anne
  • release-10.4.1
  • dev
  • 10.4.1_pesei
  • v11_beta
  • v10.4
  • v10.4_beta
  • v10.4_alpha
  • v9.2.0.3
  • v9.2
  • FPv9.3.2e
  • FPv9.3.2d
  • FPv9.3.2c
  • FPv9.3.2b
  • v9.2.0.2_Yosemite
  • ICR-1008
  • v10.2beta
  • FPv9.3.2a
  • fp9.3.1-20170412-nc4-coded
  • fp9.3.1-20170408-nc4
  • devlan-20161106
  • FPv9.3.1f
  • FPv9.3.1e
  • FPv9.3.1d
40 results

flexpart

  • Clone with SSH
  • Clone with HTTPS
  • Forked from Flexpart / Flexpart
    50 commits behind the upstream repository.
    Lucie Bakels's avatar
    Lucie Bakels authored
    aa1f5565
    History

    Welcome to Flexpart - The Lagrangian particle dispersion model

    This is the main development site @ University of Vienna.

    Other references:

    What is this repository for?

    • This repository contains versions of the Lagrangian model FLEXPART
    • Development versions
    • Issues on the FLEXPART model, tickets/mail
    • Feature requests for future versions

    Getting started with Flexpart

    The model is written in Fortran. It needs to be compiled for the architecture that runs it. Please have a look at the instructions on building FLEXPART available here or online. There is also a containerized version of FLEXPART available.

    Contribution guidelines

    • The version contributed should compile on a reference version of the system and compiler.

      • FLEXPART 10.4 used as a reference gfortran 5.4 on Ubuntu 16.04
      • FLEXPART 11 uses as a reference gfortran 8.5.0 on AlmaLinux 8/RockyLinux 8 or gfortran 11.4.1 on RockyLinux 9
    • Code contribution including new features and bug fixes should be complemented with appropriate tests An essential test consists of a set of input files and directories that allow FLEXPART to run. A test can be accompanied by output files for verification

    • Code review

    • report issues via mail to support

    • become an active developer and request a user account on gitlab.