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

input files #6

Open
beneslami opened this issue Aug 6, 2023 · 1 comment
Open

input files #6

beneslami opened this issue Aug 6, 2023 · 1 comment

Comments

@beneslami
Copy link

Hi.

It seems that instead of default mode, benchmarks also get an input file. For example, BT can get inputbt.data. I was wondering if there is any place where I can the input files for all benchmarks ?

Thanks

@gabriellaraujocoding
Copy link
Member

Hi.

We're sorry for our late reply.

The NPB default mode collects parameters from the file npbparams.hpp, which is generated when you compile a benchmark (it is located in the directory of the benchmark, for instance, in the BT directory). This is the correct way of using the NPB right now.

The other mode is when you read an input file, for example, as you mentioned, inputbt.data. In this case, instead of reading data from the file npbparams.hpp, the benchmark will read the inputs of inputbt.data. However, this breaks the code execution unless the values from the file inputbt.data are equal to the ones in the file npbparams.hpp.

We ported the NPB from Fortran to C++ trying to make it as similar as possible. In the original version, the parameters from inputbt.data are not treated too, which breaks the code. Thus, we will remove this alternative mode from the code soon. We did not realize that this mode was not treated. So, thank you for commenting about this.

In addition, I will answer your question about where we should place these files.data, it should go into the directory named CUDA (it is the root directory of an NPB version). That is the directory where you can put the file timer.flag too.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants