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

Remove reliance on core_model_name #388

Open
sahiljhawar opened this issue Nov 5, 2024 · 4 comments
Open

Remove reliance on core_model_name #388

sahiljhawar opened this issue Nov 5, 2024 · 4 comments
Labels
enhancement New feature or request help wanted Extra attention is needed question Further information is requested

Comments

@sahiljhawar
Copy link
Member

Remove core_model_name from model.py. Currently (if local flag is set) the model name and the SVD model names are supposed to be the same in order for it to work, however if one have multiple trained model files for same model, it is hard to use while keeping the models at one location. I want the model file to have any name and still work without relying on the modelname as the SVD directory name.

For example, if I want to use Bu2109lm model but I have two different version of the SVD i.e Bu2109lm_v1 and Bu2109lm_v2, I cannot use them unless I rename it to Bu2109lm.

Moving forward is this change worth it?

@sahiljhawar sahiljhawar added bug Something isn't working enhancement New feature or request help wanted Extra attention is needed question Further information is requested and removed bug Something isn't working labels Nov 5, 2024
@sahiljhawar sahiljhawar added this to the Models & Training milestone Nov 5, 2024
@mcoughlin
Copy link
Member

@bking-astro Will likely have an opinion here given the LANL model naming struggles.

@bking-astro
Copy link
Collaborator

I think this should be fine to change, as long as it's not a default setting to specify different names for model and svd dir. However I have be just making separate directories denoting the version or type of training with the typical "BU2019lm" model dir inside of it.

@sahiljhawar
Copy link
Member Author

making separate directories denoting the version or type of training with the typical "BU2019lm" model dir inside of it.

@bking-astro Can you explain more?

@bking-astro
Copy link
Collaborator

I would just have, for example, /lustre/scratch5/bking/svdmodels/Bu2019lm_smoothed_15/Bu2019lm/Bu2019lm_tf.pkl and my svd_path would be /lustre/scratch5/bking/svdmodels/Bu2019lm_smoothed_15/.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request help wanted Extra attention is needed question Further information is requested
Projects
None yet
Development

No branches or pull requests

3 participants