My Community

Hello,

I have been trying to calculate the transport properties using the SERTA ELPH_SCATTERING_APPROX. The calculations crash with an error about failing to open the phelel_params.hdf5 file. When I checked the files, it turns out VASP did not generate the phelel_params.hdf5 file. I have checked the wiki and made sure to include the "ELPH_POT_GENERATE = True" tag to generate the file. Nevertheless, it was not created.

Next, I tried using the phelel package and generated the phelel_params.hdf5 file separately. However, when VASP reached the ELPH step it crashed again with no error in the standard output file but reported a bug in the standard error file and asked to file a bug report.

I have attached the my files. Maybe I am doing something wrong. Your support is greatly appreciated.

Thank you

Hello,

Thanks for reaching out. Running the electron-phonon code in VASP is at minimum a two-step process. A brief overview of the workflow is given on the electron-phonon caterogy page.

The generation of the phelel_params.hdf5 is the first step of the process and it requires a supercell (you will have to make sure that this cell is large enough by converging the final result with respect to the supercell size). You can do this either via ELPH_POT_GENERATE or via the phelel method, as detailed here. You must not set any of the electron-phonon tags related to transport. The transport calculation comes in the second step which uses a unit cell.

The second step is the actual electron-phonon calculation. This step requires the phelel_params.hdf5 file as input. In this step, we use a primitive cell (this primitive cell must match the unit cell found during the previous supercell calculation, or you specify it explicitly using ELPH_POT_LATTICE during the previous step). This is where you can follow the documentation on calculating transport coefficients.

Let me know if that works for you.

Thank you for the reply. I followed the instructions from your reply. However, in the first step after the finite difference stages were done I got this error message: "SmithNormalForm routine failed because the input matrix had a negative determinant". What does this error mean? Maybe my supercell is not large enough?

Thank you.

This is a bit unexpected. It might be due to a bug, but I will look into it. I'm sorry for the inconvenience caused by this issue.

In the meantime, could you send me your input files for this new calculation? I would like to reproduce it on my end, so that we can include a potential fix in the upcoming patch release.

Thank you for your support. I have attached my input files.

I have used the phelel package to generate the phelel_params.hdf5 file. After that, I have run the transport calculation step. However, the calculations crash with an error in the std.err file stating a bug in the code.

 -----------------------------------------------------------------------------
|                     _     ____    _    _    _____     _                     |
|                    | |   |  _ \  | |  | |  / ____|   | |                    |
|                    | |   | |_) | | |  | | | |  __    | |                    |
|                    |_|   |  _ <  | |  | | | | |_ |   |_|                    |
|                     _    | |_) | | |__| | | |__| |    _                     |
|                    (_)   |____/   \____/   \_____|   (_)                    |
|                                                                             |
|     internal error in: wap.F  at line: 3342                                 |
|                                                                             |
|     HDF5 call in wap.F:3342 produced error: 3                               |
|                                                                             |
|     If you are not a developer, you should not encounter this problem.      |
|     Please submit a bug report.                                             |
|                                                                             |
 -----------------------------------------------------------------------------

Can you kindly check it out?
Note: when running the phelel package, you need to in include the --fft-mesh tag to generate the phelel_params.hdf5 file (i.e. --fft-mesh 18 18 18). Otherwise the file will not be created. For some reason this is not mentioned in their wiki nor examples on Github. I have found it while digging through the code after encountering this issue.
https://github.com/phonopy/phelel/blob/ ... vatives.py on line 119

Your support is highly appreciated

Hello again,

I have spent some time this week to investigate this issue. First, I have determined that the SmithNormalForm issue is due to not specifying the FFT grid of the primitive cell via ELPH_POT_FFT_MESH. This is not stated clearly on the wiki and it's obviously a problem. Therefore, I have created a patch for the current electron-phonon code that can automatically determine the FFT grid of the primitive cell inside VASP. You can still supply it via ELPH_POT_FFT_MESH, but now the error message no longer shows up when running ELPH_POT_GENERATE=True.

Next, I have included useful information in the standard output and the OUTCAR when running with ELPH_POT_GENERATE=True. This includes the primitive FFT mesh and the primitive lattice vectors. The latter can be supplied via ELPH_POT_LATTICE, but are otherwise taken from the primitive cell that is found by VASP.

Furthermore, the primitive cell is now written to a new primitive POSCAR file, but the exact naming is not yet decided. Documentation on the wiki will follow as soon as this feature is available.

While digging through the code, I have encountered a related bug that is currently causing some calculations to fail, which you can read about here at the top of the list.

Finally, all of this will be available in the next patch release of VASP (coming very very soon).

Now, to your most recent issue, I will relay the information about phelel to the developer, but please keep in mind that we do not maintain the phelel package.

The bug message regarding wap.F that you encountered could, however, be happening on our side. Therefore, could I ask you once again to provide the input and output files so that I may reproduce the issue on my side?

Thank you for your patience. I hope that we can quickly implement all these fixes so that you can enjoy the new electron-phonon code more smoothly.

Kind regards