RosettaCommons / RosettaCommons/RFdiffusion
RuntimeError: Index put requires the source and destination dtypes match, got Long for the destination and Int for the source.
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 3.1k
- Forks
- 644
- PR merge metrics
- No merged PRs in 30d
Description
[2023-09-20 18:29:17,264][rfdiffusion.inference.model_runners][INFO] - Using contig: ['A1-250/0 150-150']
Error executing job with overrides: ['inference.output_prefix=./', 'inference.input_pdb=C:\Users\adminisiterlator\Desktop\wanglesheishishei1.pdb', 'contigmap.contigs=[A1-250/0 150-150]', 'inference.output_prefix=testoutputs/binder_test', 'inference.num_designs=1']
Traceback (most recent call last):
File "C:\Users\adminisiterlator\RFdiffusion\scripts\run_inference.py", line 84, in main
x_init, seq_init = sampler.sample_init()
^^^^^^^^^^^^^^^^^^^^^
File "c:\users\adminisiterlator\rfdiffusion\rfdiffusion\inference\model_runners.py", line 354, in sample_init
seq_t[contig_map.hal_idx0] = seq_orig[contig_map.ref_idx0]
~~~~~^^^^^^^^^^^^^^^^^^^^^
RuntimeError: Index put requires the source and destination dtypes match, got Long for the destination and Int for the source.
Set the environment variable HYDRA_FULL_ERROR=1 for a complete stack trace.
I didn't understand why this happened
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with scripts/run_inference.py and rfdiffusion/inference/model_runners.py, especially sample_init at the reported traceback line. Reproduce the command from the issue and inspect the dtypes of seq_t and seq_orig at the failing assignment. Done means the reported inference run no longer raises the dtype mismatch.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- bioinformatics, machine-learning
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100