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

Project Name Issue When Using Hooks #28

Open
rbreslavsky opened this issue Jan 9, 2024 · 1 comment
Open

Project Name Issue When Using Hooks #28

rbreslavsky opened this issue Jan 9, 2024 · 1 comment

Comments

@rbreslavsky
Copy link

When using CAPE and pyfun, I prefer not to use a template fun3d.nml. This actually works quite well, as I can use Python "hooks" to populate the entire FUN3D namelist file for a given simulation / case. However, I've had some difficulty pertaining to the project_rootname field in the &project namelist. I've tried to define it in my namelist Python hook, but it keeps getting overwritten such that project_rootname = "pyfun". Is this a bug?

@nasa-ddalle
Copy link
Collaborator

In this case, you could call this a bug, but it would take some thought to fix it. The reason is that pyfun needs to know the project_rootname early in the process, and it's possible that your hooks haven't run yet when it needs that. (For example it writes mesh file names.)

I think you can work around this issue by putting this in your JSON file:

"Fun3D": {
    "project": {
        "project_rootname": "yourproject"
    }
}

You can set it to anything you want. If you want it to be different for different cases in the same run matrix, you can have your InitFunction hook set this value. But having it set in the JSON like this should fix the particular issue you're having.

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