Frame-level bit-allocation of DMC model from ACM MM2022
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
- Issue type
- Documentation
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- python
- Domain
- machine-learning
Research direction
Start by following the provided test instruction and inspecting the per-frame PSNR values in the output JSON for Jockey. Compare those observations with the released code and the ACM MM2022 paper. Done means documenting how the DMC implementation allocates bits between frames or explaining the observed phenomenon.
Written by the indexing model from the issue text.
Description
Hello, thank you for the work and sharing your code.
We have a question after running the program following the provided test instruction. We drawing the per-frame PSNR value recorded in the output json file (as shown in the figure below), we found that there seems to be a frame-level bit allocation mechanism in the DMC model. However, we could not find any information on frame-level bit allocation in the proposed paper or in the released code.
Can you provide some details on how your implementation does the bit allocation between each frame or any insight into such phenomenon?
- Dominant language
- Python
- Stars
- 829
- Forks
- 138
- PR merge metrics
- No merged PRs in 30d
Getting set up
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.
More from microsoft/DCVC
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 45/100
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
PedestrianDynamics/pyFDS-Evac#199 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
521xueweihan/HelloGitHub#3790 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
sandialabs/atlas-ui-3#978 ·
Maintainers usually reply within 1 day
-
area: tests perceived difficulty: 2
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Nitjsefnie-Harness-Commons/daedalus#1255 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
EleutherAI/lm-evaluation-harness#4256 ·
Maintainers usually reply within 1 day