Incompatibility between --elbdm_scheme=HYBRID and Output_DumpData_Part()

[hyschive]

🔎 What happened?

Running the VortexPairLinear_Hybrid test leads to the following error message:

ERROR : Prepare_PatchData() for hybrid scheme currently does not support preparing the density and the real/imaginary part of the wave function simultaneousl
This is probably due to operation (b2-3-1) and can probably be easily fixed.
        Rank <1>, file <Main/Prepare_PatchData.cpp>, line <257>, function <Prepare_PatchData>

📃 Steps to reproduce

The issue can be reproduced with the default configuration of the VortexPairLinear_Hybrid test.

⌚ Commit hash

6312ecf

🔧 Configuration command

python3 configure.py --model=ELBDM --elbdm_scheme=HYBRID --hdf5=true --mpi=true "$@"

🔨 Source files modified

None

💻 Operating system

linux (x86)

💾 Machine configuration file

spock_intel.config

🔖 Related topics

• Hydro
• MHD
• FDM
• AMR
• Gravity
• Particle
• Parallelization
• GPU
• Memory
• YT
• Tool
• Docs
• Other

💬 Additional information

The issue is likely caused by specifying _TOTAL when calling Prepare_PatchData() in the FDM hybrid scheme. We should try to remove the following constraints in Prepare_PatchData()

   if (   (  ( (TVarCC & _REAL) && !(TVarCC & _IMAG) )  ||  ( !(TVarCC & _REAL) && (TVarCC & _IMAG) )  )
          &&  amr->use_wave_flag[lv]   )
      Aux_Error( ERROR_INFO, "%s() for hybrid scheme currently requires that the real and imaginary parts of the wave function are prepared together !!\n"
                             "This is probably due to operation (b2-3-1) and can probably be easily fixed.\n", __FUNCTION__ );

   if ( ( TVarCC & _DENS )  &&  ( TVarCC & (_REAL | _IMAG) )  &&
        GhostSize > 0  &&  lv > 0  &&  amr->use_wave_flag[lv]  &&  !amr->use_wave_flag[lv-1] )
      Aux_Error( ERROR_INFO, "%s() for hybrid scheme currently does not support preparing the density "
                             "and the real/imaginary part of the wave function simultaneously !!\n"
                             "This is probably due to operation (b2-3-1) and can probably be easily fixed.\n", __FUNCTION__ );