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

runDLKcat(): use DLKcat.tsv in a different directory #392

Closed
edkerk opened this issue Oct 1, 2024 Discussed in #389 · 2 comments
Closed

runDLKcat(): use DLKcat.tsv in a different directory #392

edkerk opened this issue Oct 1, 2024 Discussed in #389 · 2 comments
Labels
fixed in develop Has already been addressed in develop branch

Comments

@edkerk
Copy link
Member

edkerk commented Oct 1, 2024

Discussed in #389

Originally posted by PkiwiBird August 8, 2024
It is possible to modify the directory where DLKcat.tsv is stored, with:
writeDLKcatInput(ecLiverMl,[],[],[],'path_2_light_DLKcat.tsv',true)
but how to use that file as input for runDLKcat() ?
This is useful if we want to save the files of DLKcat.tsv for the full and light models separately, as they are different.
runDLKcat() uses modelAdapter.params.
Is there a way to run runDLKcat() using as input DLKcat.tsv stored in a different directory than modelAdapter.params?

@edkerk
Copy link
Member Author

edkerk commented Oct 1, 2024

runDLKcat has the filename and path hard-coded in the python command to run DLKcat. It should indeed be possible to tell runDLKcat which file to use as an input (and the output file as well). This can be implemented, but it will take a little while before I have time to do this.

As a workaround you could use MATLAB's movefile command to rename the input file just before running runDLKcat, and rename it again after runDLKcat is done.

@edkerk
Copy link
Member Author

edkerk commented Oct 13, 2024

@PkiwiBird, does the modified runDLKcat in #394 work for you?

@edkerk edkerk mentioned this issue Oct 13, 2024
2 tasks
@edkerk edkerk added the fixed in develop Has already been addressed in develop branch label Oct 14, 2024
@edkerk edkerk closed this as completed Oct 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
fixed in develop Has already been addressed in develop branch
Projects
None yet
Development

No branches or pull requests

1 participant