Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

TBG error #3247

Closed
cbontoiu opened this issue May 19, 2020 · 7 comments
Closed

TBG error #3247

cbontoiu opened this issue May 19, 2020 · 7 comments
Labels
machine/system machine & HPC system specific issues question

Comments

@cbontoiu
Copy link
Contributor

Hello,

I got a strange error on a model as soon as I decreased the laser wavelength down to 5.5 nm. All was fine for wavelengths between 27.5 nm to 110 nm. The error is shown in the image below and the model is attached, but maybe you can give me a hint without needing to run it.

image

Thank you,
Cristian

one-tube-plates-parallel-LX.zip

@sbastrakov
Copy link
Member

sbastrakov commented May 20, 2020

Hi @cbontoiu . From the error message it seems to be related to your environment settings, not the physics-related simulation parameters. Could you re-check that you sourced your picongpu profile before running tbg? Variables like TBG_Author and others in the list are populated through the profile, so them missing suggests the profile has not been sourced.

@sbastrakov sbastrakov added machine/system machine & HPC system specific issues question labels May 20, 2020
@cbontoiu
Copy link
Contributor Author

cbontoiu commented May 20, 2020

Hello @sbastrakov
Thank you for your help. In my case working on a local machine with a single GPU via Spack, I don't have a profile to source. However, every time I launch a terminal, the .bashrc file is sourced and here are the relevant variables inside it.

image

I restarted the terminal, sourced .bashrc explicilty, loaded picongpu with adios as always, compiled fine but the same error appears. I don't know if the message "Argument list too long" tells something.

image

@sbastrakov
Copy link
Member

Thanks for more information. Unfortunately, I really do not have a good idea. Perhaps @psychocoderHPC does?

@cbontoiu
Copy link
Contributor Author

cbontoiu commented May 23, 2020

I have uninstalled picongpu and then resintalled picongpu@develop +adios. Still the same error appears but, this time there is also something about a broken pipe

image

@cbontoiu
Copy link
Contributor Author

cbontoiu commented May 24, 2020

Another hint comes from the fact that the same model gives a different error on another computer. It fails at compilation time in this case.

/home/cristi/PIC_INPUT/one-tube-plates-parallel-LX/include/alpaka/elem/Traits.hpp(36): error #135: namespace "std" has no member "remove_volatile_t"
/home/cristi/PIC_INPUT/one-tube-plates-parallel-LX/include/alpaka/elem/Traits.hpp(36): error #65: expected a ";"
/home/cristi/PIC_INPUT/one-tube-plates-parallel-LX/include/alpaka/elem/Traits.hpp(48): error #135: namespace "std" has no member "enable_if_t"
/home/cristi/PIC_INPUT/one-tube-plates-parallel-LX/include/alpaka/elem/Traits.hpp(48): error #439: expected a ">"
/home/cristi/PIC_INPUT/one-tube-plates-parallel-LX/include/alpaka/elem/Traits.hpp(51): warning #12-D: parsing restarts here after previous syntax error
/home/cristi/PIC_INPUT/one-tube-plates-parallel-LX/include/alpaka/idx/Traits.hpp(50): error #135: namespace "std" has no member "enable_if_t"
/home/cristi/PIC_INPUT/one-tube-plates-parallel-LX/include/alpaka/idx/Traits.hpp(50): error #439: expected a ">"

@psychocoderHPC
Copy link
Member

IMO this issue is mixing two different issues.

home/cristi/PIC_INPUT/one-tube-plates-parallel-LX/include/alpaka/elem/Traits.hpp(36): error #135: namespace "std" has no member "remove_volatile_t"

This could be an issue because the develop branch switched to C++14 with #3242 but the spack recipe is not tested for it.

The other issue Argument list to long could come from the commented out TBG_plugins in the cfg file. @cbontoiu could you please remove this section.

@cbontoiu We will handle in this issue only the tbg issue. If the other issue with the compile still exists please open a new issue.

@cbontoiu
Copy link
Contributor Author

cbontoiu commented May 25, 2020

Thnak you,

Indeed the runtime problem was due to both TBG_plugins being commented. The simulation started to work when I uncommented one of them. It a silly mistake from my side but maybe the error message could be made more instructive in the future?

image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
machine/system machine & HPC system specific issues question
Projects
None yet
Development

No branches or pull requests

3 participants