Custom Query (210 matches)
Results (4 - 6 of 210)
Ticket | Resolution | Summary | Owner | Reporter |
---|---|---|---|---|
#189 | fixed | FLEXPART Release - Consistent Cs-137 isotope releases and output interpretation | acheloni | |
Description |
Hello everyone, I'm trying to correctly set releases to simulate a nuclear plant incident. I tried with masses (Kg) to specify the release. An incident such as Fukushima or Chernobyl with about 1016 Bq Cs-137 radionuclide activity, the corresponding mass released in the atmosphere is about 3.2Kg. With "3.2" set for masses and a 12hr release, the resulting Cs-137 forecasted concentrations are lower than 10-13 (Kg/m3 ?). Is that a sounding result or I'm missing something? Generally, what's the "best" way to configure a nuclear plant incident? Thank you in advance Alessandro Cheloni |
|||
#99 | fixed | Flexpart-WRF v3.1 OMP | jbrioude | acificap |
Description |
Hi! I am trying to compile FLEXPART-WRF v3.1 on a linux x86_64 machine. I have successfully compiled it in serial mode, however I am having difficulty running the program once it is compiled with openMP. I compile as follows: $ OMP_NUM_THREADS=2 make -f makefile.mom omp and the compilation runs fine. However, when I run the program, it almost immediately throws a seg fault. I have a feeling this has to do with how openmp is setting the stack size on compilation. I tried adding the flag: "-fmax-stack-var-size=n" for various numbers of bit, n, and this compiles fine, (it does give plenty of warnings that this overrides -frecursive); however, then I run into issues with the variable maxomp in par_mod.f90 . How can I get the compiler to set the appropriate stack size? |
|||
#100 | worksforme | Flexpart-WRF grid_flux Output | somebody | acificap |
Description |
I've been reading the documentation, and there's very little to say at all about the IFLUX option. I have three questions:
|