-
Notifications
You must be signed in to change notification settings - Fork 301
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
SaShiMi generation script errors out with own models #32
Comments
Hi Stefan, The model changed recently and we are planning to revisit it next week to make sure the Sashimi code is working. |
Hi Albert, Okay perfect, thank you very much for the insanely quick response! I'll try it out with the state from the v2 tag and report back if I encounter any other issues. Other than that, maybe one more quick question for now: Does it make sense for me to get it working with v2 or would you suggest I rather wait a week or two until you're mostly done with your current iterations? |
It probably depends on what you want to use it for. What I expect is that the training code ( |
Hi there, I quickly wanted to share I run into similar issues when simply trying to generate samples following the instructions, without any changes: python -m sashimi.generation --model sashimi --dataset youtubemix --n_samples 32 --sample_len 16000 throws
I haven't yet tried the steps @stefan-baumann suggested to fix this error though. |
@albertfgu any updates on this? I trained a model on the most recent changes on GitHub and still get the same error when trying to generate. |
I would also be happy to implement the fix myself if you can give me some systematic hints on what has been changed that causes this error. |
The model should work with v2 of the codebase, which is the official Sashimi release. Can you describe your setup and paste the command you ran and the error it gave? |
Probably still the same issues I described in my initial post. There have been no changes to relevant parts of the code afaik. I can confirm that I got v2 to work though. |
@stefan-baumann Good to hear that you could make it work! Can you tell me the hash of the commit that works for you? |
I trained a model from scratch on commit 6cbc09a on my own dataset using:
For generation later I use:
|
I took the v2 tag (74d2706) and backported some of the later commits (especially the kernel stuff) @davidmrau |
v2 should still work - it sounds like Stefan is confirming that it works modulo PyTorch versions. |
You should be able to load models trained with the current codebase by modifying the generation script with the appropriate flags, for example just removing the |
I'll give it a try. |
Sorry for how long it took to get this all out. The current version of the codebase should have
I tested as many things as I could, but please file a new issue for any problems that may arise |
Hey, first of all, great work with the repository, I don't think I've worked with a repository for a paper that's so extensive and well-structured so far.
I'm currently trying to train the SaShiMi model on my own dataset (following your guide here: #23), and I run into some issues when trying to generate samples with the trained model.
In case this is relevant, I'm trying to do inference on the checkpoint files, and I changed the number of layers (
model.n_layers
) to 4 to accommodate for the memory limitations of my GPU. Apart from that, I have done no changes to any of the training and model (code) except for switching the dataset to my own.When I try to call the
generation.py
script now, I run into a range of errors:hurwitz
parameter does not exist anymore, and thesetup_step
methods don't seem to correctly accept (or rather pass them downstream) the mode argument. I "fixed" this by removing thehurwitz
argument override and by adding the mode argument to allmodule.setup_step()
methods and just passing it downstream as required.model.layer.postact=null
causes thestate_dict
to not load successfully anymore, giving me the following error:Does this mean that I should rename those keys manually (there's a fairly clear correspondence) to make it work after changing the activation?
mode
parameter inmodule.setup_step()
, I still get this error:Do you have any idea what might be causing this and maybe an idea about how to fix/circumvent this?
It'd be awesome if you could help point me in the right direction with this.
Best,
Stefan
The text was updated successfully, but these errors were encountered: