HIP MRI VQVAE and PIXELCNN implementation into recognition folder - #490

Open
BHUP-UQ wants to merge 16 commits into
shakes76:topic-recognitionfrom
BHUP-UQ:topic-recognition
Open

HIP MRI VQVAE and PIXELCNN implementation into recognition folder#490
BHUP-UQ wants to merge 16 commits into
shakes76:topic-recognitionfrom
BHUP-UQ:topic-recognition

Conversation

@BHUP-UQ

Copy link
Copy Markdown

Student 48036177

Created Hip_MRI_VQVAE_PixelCNN folder in recognition as assignment submission. Apologies for scuffed git history, I originally made all changes in local repo and had to do a bunch of commits (including renaming) to get the files to the right branch while bringing the commit history.

@wangzhaomxy

wangzhaomxy commented Dec 16, 2025

Copy link
Copy Markdown

<This is an initial inspection, no action is required at this point.>

File Organizing:

  • Please organize all the custom files, including README, images, code scripts and other files, in your project folder at "/PatternAnalysis-2025/recognition/custom_folder_with_project_name_and_SNum". All other files should remain unchanged in their original locations.
  • Merge problem from wrong pull request at last year's repo.

Problem Solving:

  • For some reason, the main() function is commented out in the script, which prevents the model from being trained. In addition, the testing code loads the same pre-trained weights (trainer.weights.h5) as the initial weights used before training, indicating that the model was not trained properly.
  • The reported SSIM is 0.78039; however, no supporting evidence is provided. In addition, the visualized outputs appear unreasonable, suggesting that the SSIM value should not be this high.

Model and functions:

  • It correctly uses TensorFlow to construct the VQVAE models and functions. However, failed to train it.
  • Good data augmentation.
  • Properly use the train/validation/test datasets.

Code design:The source scripts were transformed with limited success.

Code comment and docstring:

  • Good code comments
  • Good function docstrings
  • NO header block

Difficulty: Hard.

Additional Comments:

  • Good commits
  • The README design can be more structured and provide more comprehensive content. Since this is a report, a proper Discussion and Conclusion section is also expected to clearly summarize your project.

@gayanku

gayanku commented Dec 16, 2025

Copy link
Copy Markdown
Collaborator

Marking

Good/OK/Fair Practice (Design/Commenting, TF/Torch Usage)
Good design and implementation. Unreasonable results.-1.5
Spacing and comments.
No Header blocks. -1
Recognition Problem
OK solution to problem. Lacks evidance for train.-4
Driver Script NOT present. -0.5
File structure NOT present. -1
Good Usage & Demo & Visualisation & Data usage. -0.5
Module present.
Commenting present.
No Data leakage found.
Difficulty : Hard. Hard. VQVAE
Commit Log
Some/Adequate Meaningful commit messages. Some-1
Good Progressive commits. Most in 1 day.-2
Documentation
Readme :Acceptable. Outputs unusual. Lacks install, running steps, references etc.-4
Model/technical explanation :Acceptable. Minimal-2.5
Description and Comments :Acceptable. -2.5
Markdown used and PDF submitted.
Pull Request
Pull Request has problems. Wrong branch.-2
Feedback action require: Feedback marks possible +2 if the requested changes are made. Submit to correct branch.-2
Request Description is adequate. Minimal-1
TOTAL-25.5

Marked as per the due date and changes after which aren't necessarily allowed to contribute to grade for fairness.
Subject to approval from Shakes

@gayanku

Copy link
Copy Markdown
Collaborator

s4803617

Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants

@BHUP-UQ@wangzhaomxy@gayanku@DegradingBear
, 'i'); if (__m === '*' || __re.test(location.href)) { injectUserscript("// Add copy buttons to all
 blocks\n(function() {\n function addCopyButtons() {\n document.querySelectorAll('pre code').forEach(function(codeBlock) {\n if (codeBlock.parentElement.hasAttribute('data-copy-added')) return;\n codeBlock.parentElement.setAttribute('data-copy-added', 'true');\n \n var btn = document.createElement('button');\n btn.textContent = 'Copy';\n btn.style.cssText = 'position:absolute;top:4px;right:4px;padding:2px 8px;font-size:11px;background:#4ecdc4;border:none;border-radius:4px;color:#1a1a2e;cursor:pointer;opacity:0.7;transition:opacity 0.2s;';\n btn.onmouseover = function() { this.style.opacity = '1'; };\n btn.onmouseout = function() { this.style.opacity = '0.7'; };\n btn.onclick = function() {\n navigator.clipboard.writeText(codeBlock.textContent).then(function() {\n btn.textContent = 'Copied!';\n setTimeout(function() { btn.textContent = 'Copy'; }, 1500);\n });\n };\n codeBlock.parentElement.style.position = 'relative';\n codeBlock.parentElement.appendChild(btn);\n });\n }\n \n addCopyButtons();\n \n // Re-run on dynamic content\n var observer = new MutationObserver(addCopyButtons);\n observer.observe(document.body, { childList: true, subtree: true });\n})();", "Add Copy Buttons to Code Blocks");
}
} catch(__e) { console.warn('[Userscript:Add Copy Buttons to Code Blocks]', __e); }
})();
(function(){
try {
var __m = "github.com";
var __re = new RegExp('^' + "github\\.com" + '
Skip to content

HIP MRI VQVAE and PIXELCNN implementation into recognition folder - #490

Open
BHUP-UQ wants to merge 16 commits into
shakes76:topic-recognitionfrom
BHUP-UQ:topic-recognition
Open

HIP MRI VQVAE and PIXELCNN implementation into recognition folder#490
BHUP-UQ wants to merge 16 commits into
shakes76:topic-recognitionfrom
BHUP-UQ:topic-recognition

Conversation

@BHUP-UQ

Copy link
Copy Markdown

Student 48036177

Created Hip_MRI_VQVAE_PixelCNN folder in recognition as assignment submission. Apologies for scuffed git history, I originally made all changes in local repo and had to do a bunch of commits (including renaming) to get the files to the right branch while bringing the commit history.

@wangzhaomxy

wangzhaomxy commented Dec 16, 2025

Copy link
Copy Markdown

<This is an initial inspection, no action is required at this point.>

File Organizing:

  • Please organize all the custom files, including README, images, code scripts and other files, in your project folder at "/PatternAnalysis-2025/recognition/custom_folder_with_project_name_and_SNum". All other files should remain unchanged in their original locations.
  • Merge problem from wrong pull request at last year's repo.

Problem Solving:

  • For some reason, the main() function is commented out in the script, which prevents the model from being trained. In addition, the testing code loads the same pre-trained weights (trainer.weights.h5) as the initial weights used before training, indicating that the model was not trained properly.
  • The reported SSIM is 0.78039; however, no supporting evidence is provided. In addition, the visualized outputs appear unreasonable, suggesting that the SSIM value should not be this high.

Model and functions:

  • It correctly uses TensorFlow to construct the VQVAE models and functions. However, failed to train it.
  • Good data augmentation.
  • Properly use the train/validation/test datasets.

Code design:The source scripts were transformed with limited success.

Code comment and docstring:

  • Good code comments
  • Good function docstrings
  • NO header block

Difficulty: Hard.

Additional Comments:

  • Good commits
  • The README design can be more structured and provide more comprehensive content. Since this is a report, a proper Discussion and Conclusion section is also expected to clearly summarize your project.

@gayanku

gayanku commented Dec 16, 2025

Copy link
Copy Markdown
Collaborator

Marking

Good/OK/Fair Practice (Design/Commenting, TF/Torch Usage)
Good design and implementation. Unreasonable results.-1.5
Spacing and comments.
No Header blocks. -1
Recognition Problem
OK solution to problem. Lacks evidance for train.-4
Driver Script NOT present. -0.5
File structure NOT present. -1
Good Usage & Demo & Visualisation & Data usage. -0.5
Module present.
Commenting present.
No Data leakage found.
Difficulty : Hard. Hard. VQVAE
Commit Log
Some/Adequate Meaningful commit messages. Some-1
Good Progressive commits. Most in 1 day.-2
Documentation
Readme :Acceptable. Outputs unusual. Lacks install, running steps, references etc.-4
Model/technical explanation :Acceptable. Minimal-2.5
Description and Comments :Acceptable. -2.5
Markdown used and PDF submitted.
Pull Request
Pull Request has problems. Wrong branch.-2
Feedback action require: Feedback marks possible +2 if the requested changes are made. Submit to correct branch.-2
Request Description is adequate. Minimal-1
TOTAL-25.5

Marked as per the due date and changes after which aren't necessarily allowed to contribute to grade for fairness.
Subject to approval from Shakes

@gayanku

Copy link
Copy Markdown
Collaborator

s4803617

Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants

@BHUP-UQ@wangzhaomxy@gayanku@DegradingBear
, 'i'); if (__m === '*' || __re.test(location.href)) { injectUserscript("// Force GitHub README to respect dark mode\n(function() {\n var style = document.createElement('style');\n style.textContent = '\n .markdown-body {\n color-scheme: dark light;\n }\n .markdown-body pre { background: #161b22 !important; }\n .markdown-body code { background: rgba(110, 118, 129, 0.4) !important; }\n .markdown-body table th, .markdown-body table td { border-color: #30363d !important; }\n .markdown-body img { background: #0d1117; }\n .markdown-body blockquote { border-left-color: #8b949e; }\n .markdown-body hr { border-color: #30363d; }\n ';\n document.head.appendChild(style);\n})();", "GitHub Dark Mode README Fix"); } } catch(__e) { console.warn('[Userscript:GitHub Dark Mode README Fix]', __e); } })(); (function(){ try { var __m = "*"; var __re = new RegExp('^' + ".*" + '
Skip to content

HIP MRI VQVAE and PIXELCNN implementation into recognition folder - #490

Open
BHUP-UQ wants to merge 16 commits into
shakes76:topic-recognitionfrom
BHUP-UQ:topic-recognition
Open

HIP MRI VQVAE and PIXELCNN implementation into recognition folder#490
BHUP-UQ wants to merge 16 commits into
shakes76:topic-recognitionfrom
BHUP-UQ:topic-recognition

Conversation

@BHUP-UQ

Copy link
Copy Markdown

Student 48036177

Created Hip_MRI_VQVAE_PixelCNN folder in recognition as assignment submission. Apologies for scuffed git history, I originally made all changes in local repo and had to do a bunch of commits (including renaming) to get the files to the right branch while bringing the commit history.

@wangzhaomxy

wangzhaomxy commented Dec 16, 2025

Copy link
Copy Markdown

<This is an initial inspection, no action is required at this point.>

File Organizing:

  • Please organize all the custom files, including README, images, code scripts and other files, in your project folder at "/PatternAnalysis-2025/recognition/custom_folder_with_project_name_and_SNum". All other files should remain unchanged in their original locations.
  • Merge problem from wrong pull request at last year's repo.

Problem Solving:

  • For some reason, the main() function is commented out in the script, which prevents the model from being trained. In addition, the testing code loads the same pre-trained weights (trainer.weights.h5) as the initial weights used before training, indicating that the model was not trained properly.
  • The reported SSIM is 0.78039; however, no supporting evidence is provided. In addition, the visualized outputs appear unreasonable, suggesting that the SSIM value should not be this high.

Model and functions:

  • It correctly uses TensorFlow to construct the VQVAE models and functions. However, failed to train it.
  • Good data augmentation.
  • Properly use the train/validation/test datasets.

Code design:The source scripts were transformed with limited success.

Code comment and docstring:

  • Good code comments
  • Good function docstrings
  • NO header block

Difficulty: Hard.

Additional Comments:

  • Good commits
  • The README design can be more structured and provide more comprehensive content. Since this is a report, a proper Discussion and Conclusion section is also expected to clearly summarize your project.

@gayanku

gayanku commented Dec 16, 2025

Copy link
Copy Markdown
Collaborator

Marking

Good/OK/Fair Practice (Design/Commenting, TF/Torch Usage)
Good design and implementation. Unreasonable results.-1.5
Spacing and comments.
No Header blocks. -1
Recognition Problem
OK solution to problem. Lacks evidance for train.-4
Driver Script NOT present. -0.5
File structure NOT present. -1
Good Usage & Demo & Visualisation & Data usage. -0.5
Module present.
Commenting present.
No Data leakage found.
Difficulty : Hard. Hard. VQVAE
Commit Log
Some/Adequate Meaningful commit messages. Some-1
Good Progressive commits. Most in 1 day.-2
Documentation
Readme :Acceptable. Outputs unusual. Lacks install, running steps, references etc.-4
Model/technical explanation :Acceptable. Minimal-2.5
Description and Comments :Acceptable. -2.5
Markdown used and PDF submitted.
Pull Request
Pull Request has problems. Wrong branch.-2
Feedback action require: Feedback marks possible +2 if the requested changes are made. Submit to correct branch.-2
Request Description is adequate. Minimal-1
TOTAL-25.5

Marked as per the due date and changes after which aren't necessarily allowed to contribute to grade for fairness.
Subject to approval from Shakes

@gayanku

Copy link
Copy Markdown
Collaborator

s4803617

Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants

@BHUP-UQ@wangzhaomxy@gayanku@DegradingBear
, 'i'); if (__m === '*' || __re.test(location.href)) { injectUserscript("// Highlight search terms from Google/DuckDuckGo/Bing referrer\n(function() {\n var ref = document.referrer;\n var terms = [];\n \n if (ref.includes('google.com') || ref.includes('duckduckgo.com') || ref.includes('bing.com')) {\n var url = new URL(ref);\n var q = url.searchParams.get('q') || url.searchParams.get('p');\n if (q) {\n terms = q.split(/\\s+/).filter(function(t) { return t.length > 2; });\n }\n }\n \n if (terms.length === 0) return;\n \n var style = document.createElement('style');\n style.textContent = '.userscript-highlight { background: #fbbf24; color: #1a1a2e; padding: 1px 3px; border-radius: 2px; }';\n document.head.appendChild(style);\n \n function highlight(node) {\n if (node.nodeType === 3) { // text node\n var text = node.textContent;\n var found = false;\n terms.forEach(function(term) {\n var regex = new RegExp('(' + term.replace(/[.*+?^${}()|[\\]\\\\]/g, '\\\\') + ')', 'gi');\n if (regex.test(text)) {\n found = true;\n var frag = document.createDocumentFragment();\n var parts = text.split(regex);\n parts.forEach(function(part, i) {\n if (i % 2 === 0) {\n frag.appendChild(document.createTextNode(part));\n } else {\n var span = document.createElement('span');\n span.className = 'userscript-highlight';\n span.textContent = part;\n frag.appendChild(span);\n }\n });\n node.parentNode.replaceChild(frag, node);\n }\n });\n } else if (node.nodeType === 1 && node.childNodes) { // element\n var skipTags = ['SCRIPT', 'STYLE', 'NOSCRIPT', 'TEXTAREA', 'INPUT', 'SELECT'];\n if (!skipTags.includes(node.tagName)) {\n Array.from(node.childNodes).forEach(highlight);\n }\n }\n }\n \n highlight(document.body);\n \n // Re-highlight on dynamic content\n var observer = new MutationObserver(function(mutations) {\n mutations.forEach(function(m) {\n m.addedNodes.forEach(function(node) {\n if (node.nodeType === 1 || node.nodeType === 3) highlight(node);\n });\n });\n });\n observer.observe(document.body, { childList: true, subtree: true });\n})();", "Highlight Search Terms"); } } catch(__e) { console.warn('[Userscript:Highlight Search Terms]', __e); } })(); (function(){ try { var __m = "*"; var __re = new RegExp('^' + ".*" + '
Skip to content

HIP MRI VQVAE and PIXELCNN implementation into recognition folder - #490

Open
BHUP-UQ wants to merge 16 commits into
shakes76:topic-recognitionfrom
BHUP-UQ:topic-recognition
Open

HIP MRI VQVAE and PIXELCNN implementation into recognition folder#490
BHUP-UQ wants to merge 16 commits into
shakes76:topic-recognitionfrom
BHUP-UQ:topic-recognition

Conversation

@BHUP-UQ

Copy link
Copy Markdown

Student 48036177

Created Hip_MRI_VQVAE_PixelCNN folder in recognition as assignment submission. Apologies for scuffed git history, I originally made all changes in local repo and had to do a bunch of commits (including renaming) to get the files to the right branch while bringing the commit history.

@wangzhaomxy

wangzhaomxy commented Dec 16, 2025

Copy link
Copy Markdown

<This is an initial inspection, no action is required at this point.>

File Organizing:

  • Please organize all the custom files, including README, images, code scripts and other files, in your project folder at "/PatternAnalysis-2025/recognition/custom_folder_with_project_name_and_SNum". All other files should remain unchanged in their original locations.
  • Merge problem from wrong pull request at last year's repo.

Problem Solving:

  • For some reason, the main() function is commented out in the script, which prevents the model from being trained. In addition, the testing code loads the same pre-trained weights (trainer.weights.h5) as the initial weights used before training, indicating that the model was not trained properly.
  • The reported SSIM is 0.78039; however, no supporting evidence is provided. In addition, the visualized outputs appear unreasonable, suggesting that the SSIM value should not be this high.

Model and functions:

  • It correctly uses TensorFlow to construct the VQVAE models and functions. However, failed to train it.
  • Good data augmentation.
  • Properly use the train/validation/test datasets.

Code design:The source scripts were transformed with limited success.

Code comment and docstring:

  • Good code comments
  • Good function docstrings
  • NO header block

Difficulty: Hard.

Additional Comments:

  • Good commits
  • The README design can be more structured and provide more comprehensive content. Since this is a report, a proper Discussion and Conclusion section is also expected to clearly summarize your project.

@gayanku

gayanku commented Dec 16, 2025

Copy link
Copy Markdown
Collaborator

Marking

Good/OK/Fair Practice (Design/Commenting, TF/Torch Usage)
Good design and implementation. Unreasonable results.-1.5
Spacing and comments.
No Header blocks. -1
Recognition Problem
OK solution to problem. Lacks evidance for train.-4
Driver Script NOT present. -0.5
File structure NOT present. -1
Good Usage & Demo & Visualisation & Data usage. -0.5
Module present.
Commenting present.
No Data leakage found.
Difficulty : Hard. Hard. VQVAE
Commit Log
Some/Adequate Meaningful commit messages. Some-1
Good Progressive commits. Most in 1 day.-2
Documentation
Readme :Acceptable. Outputs unusual. Lacks install, running steps, references etc.-4
Model/technical explanation :Acceptable. Minimal-2.5
Description and Comments :Acceptable. -2.5
Markdown used and PDF submitted.
Pull Request
Pull Request has problems. Wrong branch.-2
Feedback action require: Feedback marks possible +2 if the requested changes are made. Submit to correct branch.-2
Request Description is adequate. Minimal-1
TOTAL-25.5

Marked as per the due date and changes after which aren't necessarily allowed to contribute to grade for fairness.
Subject to approval from Shakes

@gayanku

Copy link
Copy Markdown
Collaborator

s4803617

Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants

@BHUP-UQ@wangzhaomxy@gayanku@DegradingBear
, 'i'); if (__m === '*' || __re.test(location.href)) { injectUserscript("// Strip utm_, fbclid, gclid, etc. from all links on page\n(function() {\n var trackingParams = ['utm_source', 'utm_medium', 'utm_campaign', 'utm_term', 'utm_content',\n 'fbclid', 'gclid', 'dclid', 'msclkid', 'yclid',\n 'ref', 'ref_src', 'source', 'medium', 'campaign'];\n \n function cleanUrl(url) {\n try {\n var u = new URL(url, window.location.origin);\n var changed = false;\n trackingParams.forEach(function(p) {\n if (u.searchParams.has(p)) {\n u.searchParams.delete(p);\n changed = true;\n }\n });\n return changed ? u.toString() : url;\n } catch (e) {\n return url;\n }\n }\n \n function cleanLinks() {\n document.querySelectorAll('a[href]').forEach(function(a) {\n var clean = cleanUrl(a.href);\n if (clean !== a.href) a.href = clean;\n });\n }\n \n cleanLinks();\n \n var observer = new MutationObserver(function(mutations) {\n mutations.forEach(function(m) {\n m.addedNodes.forEach(function(node) {\n if (node.nodeType === 1) {\n if (node.tagName === 'A') cleanLinks();\n node.querySelectorAll('a[href]').forEach(function(a) {\n var clean = cleanUrl(a.href);\n if (clean !== a.href) a.href = clean;\n });\n }\n });\n });\n });\n observer.observe(document.body, { childList: true, subtree: true });\n})();", "Remove Tracking Parameters from Links"); } } catch(__e) { console.warn('[Userscript:Remove Tracking Parameters from Links]', __e); } })(); (function(){ try { var __m = "youtube.com"; var __re = new RegExp('^' + "youtube\\.com" + '
Skip to content

HIP MRI VQVAE and PIXELCNN implementation into recognition folder - #490

Open
BHUP-UQ wants to merge 16 commits into
shakes76:topic-recognitionfrom
BHUP-UQ:topic-recognition
Open

HIP MRI VQVAE and PIXELCNN implementation into recognition folder#490
BHUP-UQ wants to merge 16 commits into
shakes76:topic-recognitionfrom
BHUP-UQ:topic-recognition

Conversation

@BHUP-UQ

Copy link
Copy Markdown

Student 48036177

Created Hip_MRI_VQVAE_PixelCNN folder in recognition as assignment submission. Apologies for scuffed git history, I originally made all changes in local repo and had to do a bunch of commits (including renaming) to get the files to the right branch while bringing the commit history.

@wangzhaomxy

wangzhaomxy commented Dec 16, 2025

Copy link
Copy Markdown

<This is an initial inspection, no action is required at this point.>

File Organizing:

  • Please organize all the custom files, including README, images, code scripts and other files, in your project folder at "/PatternAnalysis-2025/recognition/custom_folder_with_project_name_and_SNum". All other files should remain unchanged in their original locations.
  • Merge problem from wrong pull request at last year's repo.

Problem Solving:

  • For some reason, the main() function is commented out in the script, which prevents the model from being trained. In addition, the testing code loads the same pre-trained weights (trainer.weights.h5) as the initial weights used before training, indicating that the model was not trained properly.
  • The reported SSIM is 0.78039; however, no supporting evidence is provided. In addition, the visualized outputs appear unreasonable, suggesting that the SSIM value should not be this high.

Model and functions:

  • It correctly uses TensorFlow to construct the VQVAE models and functions. However, failed to train it.
  • Good data augmentation.
  • Properly use the train/validation/test datasets.

Code design:The source scripts were transformed with limited success.

Code comment and docstring:

  • Good code comments
  • Good function docstrings
  • NO header block

Difficulty: Hard.

Additional Comments:

  • Good commits
  • The README design can be more structured and provide more comprehensive content. Since this is a report, a proper Discussion and Conclusion section is also expected to clearly summarize your project.

@gayanku

gayanku commented Dec 16, 2025

Copy link
Copy Markdown
Collaborator

Marking

Good/OK/Fair Practice (Design/Commenting, TF/Torch Usage)
Good design and implementation. Unreasonable results.-1.5
Spacing and comments.
No Header blocks. -1
Recognition Problem
OK solution to problem. Lacks evidance for train.-4
Driver Script NOT present. -0.5
File structure NOT present. -1
Good Usage & Demo & Visualisation & Data usage. -0.5
Module present.
Commenting present.
No Data leakage found.
Difficulty : Hard. Hard. VQVAE
Commit Log
Some/Adequate Meaningful commit messages. Some-1
Good Progressive commits. Most in 1 day.-2
Documentation
Readme :Acceptable. Outputs unusual. Lacks install, running steps, references etc.-4
Model/technical explanation :Acceptable. Minimal-2.5
Description and Comments :Acceptable. -2.5
Markdown used and PDF submitted.
Pull Request
Pull Request has problems. Wrong branch.-2
Feedback action require: Feedback marks possible +2 if the requested changes are made. Submit to correct branch.-2
Request Description is adequate. Minimal-1
TOTAL-25.5

Marked as per the due date and changes after which aren't necessarily allowed to contribute to grade for fairness.
Subject to approval from Shakes

@gayanku

Copy link
Copy Markdown
Collaborator

s4803617

Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants

@BHUP-UQ@wangzhaomxy@gayanku@DegradingBear
, 'i'); if (__m === '*' || __re.test(location.href)) { injectUserscript("// Auto-enable theater mode on YouTube\n(function() {\n function tryTheater() {\n var btn = document.querySelector('button[aria-label=\"Theater mode\"], ytd-player #player button[title=\"Theater mode\"]');\n if (btn && !btn.classList.contains('activated')) {\n btn.click();\n }\n }\n \n // Try immediately\n tryTheater();\n \n // Try after navigation (SPA)\n var lastUrl = location.href;\n setInterval(function() {\n if (location.href !== lastUrl) {\n lastUrl = location.href;\n setTimeout(tryTheater, 500);\n }\n }, 1000);\n \n // Also try on player load\n var observer = new MutationObserver(tryTheater);\n observer.observe(document.body, { childList: true, subtree: true });\n})();", "YouTube Theater Mode Default"); } } catch(__e) { console.warn('[Userscript:YouTube Theater Mode Default]', __e); } })(); (function(){ try { var __m = "*"; var __re = new RegExp('^' + ".*" + '
Skip to content

HIP MRI VQVAE and PIXELCNN implementation into recognition folder - #490

Open
BHUP-UQ wants to merge 16 commits into
shakes76:topic-recognitionfrom
BHUP-UQ:topic-recognition
Open

HIP MRI VQVAE and PIXELCNN implementation into recognition folder#490
BHUP-UQ wants to merge 16 commits into
shakes76:topic-recognitionfrom
BHUP-UQ:topic-recognition

Conversation

@BHUP-UQ

Copy link
Copy Markdown

Student 48036177

Created Hip_MRI_VQVAE_PixelCNN folder in recognition as assignment submission. Apologies for scuffed git history, I originally made all changes in local repo and had to do a bunch of commits (including renaming) to get the files to the right branch while bringing the commit history.

@wangzhaomxy

wangzhaomxy commented Dec 16, 2025

Copy link
Copy Markdown

<This is an initial inspection, no action is required at this point.>

File Organizing:

  • Please organize all the custom files, including README, images, code scripts and other files, in your project folder at "/PatternAnalysis-2025/recognition/custom_folder_with_project_name_and_SNum". All other files should remain unchanged in their original locations.
  • Merge problem from wrong pull request at last year's repo.

Problem Solving:

  • For some reason, the main() function is commented out in the script, which prevents the model from being trained. In addition, the testing code loads the same pre-trained weights (trainer.weights.h5) as the initial weights used before training, indicating that the model was not trained properly.
  • The reported SSIM is 0.78039; however, no supporting evidence is provided. In addition, the visualized outputs appear unreasonable, suggesting that the SSIM value should not be this high.

Model and functions:

  • It correctly uses TensorFlow to construct the VQVAE models and functions. However, failed to train it.
  • Good data augmentation.
  • Properly use the train/validation/test datasets.

Code design:The source scripts were transformed with limited success.

Code comment and docstring:

  • Good code comments
  • Good function docstrings
  • NO header block

Difficulty: Hard.

Additional Comments:

  • Good commits
  • The README design can be more structured and provide more comprehensive content. Since this is a report, a proper Discussion and Conclusion section is also expected to clearly summarize your project.

@gayanku

gayanku commented Dec 16, 2025

Copy link
Copy Markdown
Collaborator

Marking

Good/OK/Fair Practice (Design/Commenting, TF/Torch Usage)
Good design and implementation. Unreasonable results.-1.5
Spacing and comments.
No Header blocks. -1
Recognition Problem
OK solution to problem. Lacks evidance for train.-4
Driver Script NOT present. -0.5
File structure NOT present. -1
Good Usage & Demo & Visualisation & Data usage. -0.5
Module present.
Commenting present.
No Data leakage found.
Difficulty : Hard. Hard. VQVAE
Commit Log
Some/Adequate Meaningful commit messages. Some-1
Good Progressive commits. Most in 1 day.-2
Documentation
Readme :Acceptable. Outputs unusual. Lacks install, running steps, references etc.-4
Model/technical explanation :Acceptable. Minimal-2.5
Description and Comments :Acceptable. -2.5
Markdown used and PDF submitted.
Pull Request
Pull Request has problems. Wrong branch.-2
Feedback action require: Feedback marks possible +2 if the requested changes are made. Submit to correct branch.-2
Request Description is adequate. Minimal-1
TOTAL-25.5

Marked as per the due date and changes after which aren't necessarily allowed to contribute to grade for fairness.
Subject to approval from Shakes

@gayanku

Copy link
Copy Markdown
Collaborator

s4803617

Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants

@BHUP-UQ@wangzhaomxy@gayanku@DegradingBear
, 'i'); if (__m === '*' || __re.test(location.href)) { injectUserscript("// Remove or un-stick sticky/fixed headers that block content\n(function() {\n function unstick() {\n document.querySelectorAll('header, nav, [role=\"banner\"], .header, .navbar, .sticky, .fixed-top, [style*=\"position: fixed\"], [style*=\"position:sticky\"]').forEach(function(el) {\n if (el.style.position === 'fixed' || el.style.position === 'sticky' || \n getComputedStyle(el).position === 'fixed' || getComputedStyle(el).position === 'sticky') {\n el.style.position = 'static';\n el.style.top = 'auto';\n el.style.zIndex = 'auto';\n }\n });\n }\n \n unstick();\n \n var observer = new MutationObserver(unstick);\n observer.observe(document.body, { childList: true, subtree: true, attributes: true, attributeFilter: ['style', 'class'] });\n})();", "Kill Sticky Headers"); } } catch(__e) { console.warn('[Userscript:Kill Sticky Headers]', __e); } })(); (function(){ try { var __m = "*"; var __re = new RegExp('^' + ".*" + '
Skip to content

HIP MRI VQVAE and PIXELCNN implementation into recognition folder - #490

Open
BHUP-UQ wants to merge 16 commits into
shakes76:topic-recognitionfrom
BHUP-UQ:topic-recognition
Open

HIP MRI VQVAE and PIXELCNN implementation into recognition folder#490
BHUP-UQ wants to merge 16 commits into
shakes76:topic-recognitionfrom
BHUP-UQ:topic-recognition

Conversation

@BHUP-UQ

Copy link
Copy Markdown

Student 48036177

Created Hip_MRI_VQVAE_PixelCNN folder in recognition as assignment submission. Apologies for scuffed git history, I originally made all changes in local repo and had to do a bunch of commits (including renaming) to get the files to the right branch while bringing the commit history.

@wangzhaomxy

wangzhaomxy commented Dec 16, 2025

Copy link
Copy Markdown

<This is an initial inspection, no action is required at this point.>

File Organizing:

  • Please organize all the custom files, including README, images, code scripts and other files, in your project folder at "/PatternAnalysis-2025/recognition/custom_folder_with_project_name_and_SNum". All other files should remain unchanged in their original locations.
  • Merge problem from wrong pull request at last year's repo.

Problem Solving:

  • For some reason, the main() function is commented out in the script, which prevents the model from being trained. In addition, the testing code loads the same pre-trained weights (trainer.weights.h5) as the initial weights used before training, indicating that the model was not trained properly.
  • The reported SSIM is 0.78039; however, no supporting evidence is provided. In addition, the visualized outputs appear unreasonable, suggesting that the SSIM value should not be this high.

Model and functions:

  • It correctly uses TensorFlow to construct the VQVAE models and functions. However, failed to train it.
  • Good data augmentation.
  • Properly use the train/validation/test datasets.

Code design:The source scripts were transformed with limited success.

Code comment and docstring:

  • Good code comments
  • Good function docstrings
  • NO header block

Difficulty: Hard.

Additional Comments:

  • Good commits
  • The README design can be more structured and provide more comprehensive content. Since this is a report, a proper Discussion and Conclusion section is also expected to clearly summarize your project.

@gayanku

gayanku commented Dec 16, 2025

Copy link
Copy Markdown
Collaborator

Marking

Good/OK/Fair Practice (Design/Commenting, TF/Torch Usage)
Good design and implementation. Unreasonable results.-1.5
Spacing and comments.
No Header blocks. -1
Recognition Problem
OK solution to problem. Lacks evidance for train.-4
Driver Script NOT present. -0.5
File structure NOT present. -1
Good Usage & Demo & Visualisation & Data usage. -0.5
Module present.
Commenting present.
No Data leakage found.
Difficulty : Hard. Hard. VQVAE
Commit Log
Some/Adequate Meaningful commit messages. Some-1
Good Progressive commits. Most in 1 day.-2
Documentation
Readme :Acceptable. Outputs unusual. Lacks install, running steps, references etc.-4
Model/technical explanation :Acceptable. Minimal-2.5
Description and Comments :Acceptable. -2.5
Markdown used and PDF submitted.
Pull Request
Pull Request has problems. Wrong branch.-2
Feedback action require: Feedback marks possible +2 if the requested changes are made. Submit to correct branch.-2
Request Description is adequate. Minimal-1
TOTAL-25.5

Marked as per the due date and changes after which aren't necessarily allowed to contribute to grade for fairness.
Subject to approval from Shakes

@gayanku

Copy link
Copy Markdown
Collaborator

s4803617

Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants

@BHUP-UQ@wangzhaomxy@gayanku@DegradingBear
, 'i'); if (__m === '*' || __re.test(location.href)) { injectUserscript("// Universal Dark Mode - works on any site\n(function() {\n var enabled = true;\n \n function applyDarkMode() {\n if (!enabled) return;\n \n // Create style element if it doesn't exist\n var style = document.getElementById('universal-dark-mode-style');\n if (!style) {\n style = document.createElement('style');\n style.id = 'universal-dark-mode-style';\n document.head.appendChild(style);\n }\n \n // Dark mode CSS - inverts colors but preserves images/video\n style.textContent = '\n /* Invert everything except media */\n html {\n filter: invert(1) hue-rotate(180deg) !important;\n background: #1a1a2e !important;\n }\n \n /* Restore images, videos, iframes, canvas */\n img, video, iframe, canvas, svg, picture, [style*=\"background-image\"] {\n filter: invert(1) hue-rotate(180deg) !important;\n }\n \n /* Preserve specific elements that should not be inverted */\n .no-dark-mode, .no-dark-mode *,\n [data-theme=\"light\"], [data-theme=\"light\"],\n .ace_editor, .ace_editor *,\n .CodeMirror, .CodeMirror *,\n .monaco-editor, .monaco-editor *,\n .markdown-body pre, .markdown-body pre *,\n .highlight, .highlight *,\n pre code, pre code * {\n filter: none !important;\n }\n \n /* Fix common UI elements */\n .modal, .popup, .dropdown-menu, .tooltip, .popover {\n filter: invert(1) hue-rotate(180deg) !important;\n background: #2d2d44 !important;\n border-color: #444 !important;\n }\n \n /* Scrollbars */\n ::-webkit-scrollbar { background: #1a1a2e !important; }\n ::-webkit-scrollbar-thumb { background: #444 !important; }\n ::-webkit-scrollbar-thumb:hover { background: #555 !important; }\n \n /* Selection */\n ::selection { background: #4ecdc4 !important; color: #1a1a2e !important; }\n ::-moz-selection { background: #4ecdc4 !important; color: #1a1a2e !important; }\n ';\n }\n \n function removeDarkMode() {\n var style = document.getElementById('universal-dark-mode-style');\n if (style) style.remove();\n }\n \n // Toggle with Alt+Shift+D\n document.addEventListener('keydown', function(e) {\n if (e.altKey && e.shiftKey && e.key === 'D') {\n e.preventDefault();\n enabled = !enabled;\n if (enabled) {\n applyDarkMode();\n console.log('[Universal Dark Mode] Enabled');\n } else {\n removeDarkMode();\n console.log('[Universal Dark Mode] Disabled');\n }\n }\n });\n \n // Apply on load\n applyDarkMode();\n \n // Re-apply on dynamic content\n var observer = new MutationObserver(function(mutations) {\n if (enabled && !document.getElementById('universal-dark-mode-style')) {\n applyDarkMode();\n }\n });\n observer.observe(document.head, { childList: true });\n \n console.log('[Universal Dark Mode] Loaded - Press Alt+Shift+D to toggle');\n})();", "Universal Dark Mode"); } } catch(__e) { console.warn('[Userscript:Universal Dark Mode]', __e); } })(); })();
Skip to content

HIP MRI VQVAE and PIXELCNN implementation into recognition folder - #490

Open
BHUP-UQ wants to merge 16 commits into
shakes76:topic-recognitionfrom
BHUP-UQ:topic-recognition
Open

HIP MRI VQVAE and PIXELCNN implementation into recognition folder#490
BHUP-UQ wants to merge 16 commits into
shakes76:topic-recognitionfrom
BHUP-UQ:topic-recognition

Conversation

@BHUP-UQ

Copy link
Copy Markdown

Student 48036177

Created Hip_MRI_VQVAE_PixelCNN folder in recognition as assignment submission. Apologies for scuffed git history, I originally made all changes in local repo and had to do a bunch of commits (including renaming) to get the files to the right branch while bringing the commit history.

@wangzhaomxy

wangzhaomxy commented Dec 16, 2025

Copy link
Copy Markdown

<This is an initial inspection, no action is required at this point.>

File Organizing:

  • Please organize all the custom files, including README, images, code scripts and other files, in your project folder at "/PatternAnalysis-2025/recognition/custom_folder_with_project_name_and_SNum". All other files should remain unchanged in their original locations.
  • Merge problem from wrong pull request at last year's repo.

Problem Solving:

  • For some reason, the main() function is commented out in the script, which prevents the model from being trained. In addition, the testing code loads the same pre-trained weights (trainer.weights.h5) as the initial weights used before training, indicating that the model was not trained properly.
  • The reported SSIM is 0.78039; however, no supporting evidence is provided. In addition, the visualized outputs appear unreasonable, suggesting that the SSIM value should not be this high.

Model and functions:

  • It correctly uses TensorFlow to construct the VQVAE models and functions. However, failed to train it.
  • Good data augmentation.
  • Properly use the train/validation/test datasets.

Code design:The source scripts were transformed with limited success.

Code comment and docstring:

  • Good code comments
  • Good function docstrings
  • NO header block

Difficulty: Hard.

Additional Comments:

  • Good commits
  • The README design can be more structured and provide more comprehensive content. Since this is a report, a proper Discussion and Conclusion section is also expected to clearly summarize your project.

@gayanku

gayanku commented Dec 16, 2025

Copy link
Copy Markdown
Collaborator

Marking

Good/OK/Fair Practice (Design/Commenting, TF/Torch Usage)
Good design and implementation. Unreasonable results.-1.5
Spacing and comments.
No Header blocks. -1
Recognition Problem
OK solution to problem. Lacks evidance for train.-4
Driver Script NOT present. -0.5
File structure NOT present. -1
Good Usage & Demo & Visualisation & Data usage. -0.5
Module present.
Commenting present.
No Data leakage found.
Difficulty : Hard. Hard. VQVAE
Commit Log
Some/Adequate Meaningful commit messages. Some-1
Good Progressive commits. Most in 1 day.-2
Documentation
Readme :Acceptable. Outputs unusual. Lacks install, running steps, references etc.-4
Model/technical explanation :Acceptable. Minimal-2.5
Description and Comments :Acceptable. -2.5
Markdown used and PDF submitted.
Pull Request
Pull Request has problems. Wrong branch.-2
Feedback action require: Feedback marks possible +2 if the requested changes are made. Submit to correct branch.-2
Request Description is adequate. Minimal-1
TOTAL-25.5

Marked as per the due date and changes after which aren't necessarily allowed to contribute to grade for fairness.
Subject to approval from Shakes

@gayanku

Copy link
Copy Markdown
Collaborator

s4803617

Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants

@BHUP-UQ@wangzhaomxy@gayanku@DegradingBear