the codes seems only have one editting way instead of two as descriped in the paper
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 13.7k
- Forks
- 1.3k
- PR merge metrics
- No merged PRs in 30d
Description
the run_variant() function in the trellis/pipelines/trellis_text_to_3d.py seems the editting way that keeps the structure unchanged and change the texture. Could you kindly tell me that how to run the "area editting" that change an area's both structure and texture?
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 by reading trellis/pipelines/trellis_text_to_3d.py and the run_variant() function to determine how the currently described editing path is exposed. Look for an existing area-editing entry point or usage example; done should mean that the repository clearly provides, or explicitly documents the absence of, a way to change both an area's structure and texture.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- computer-graphics, machine-learning
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100