exdysa commited on
Commit
57158ca
·
verified ·
1 Parent(s): ad97ed3

Update README.md

Browse files
Files changed (1) hide show
  1. README.md +25 -4
README.md CHANGED
@@ -9,7 +9,7 @@ massive thank you to [@silveroxides](https://huggingface.co/silveroxides) for ph
9
  > [!IMPORTANT]
10
  > # MIR (Machine Intelligence Resource)
11
 
12
- MIR is a naming standard, a proposed schema for ML work.<br>
13
  In its current incarnation, it looks like this:
14
 
15
  > [!NOTE]
@@ -34,7 +34,28 @@ and by the super-resolution registry code from the [Spandrel](https://github.com
34
  - Efficient and reliable compatability checks
35
  - Organized hyperparameter management
36
 
37
- ## Work to be done
38
- - Ensure compatability with [OECD AI Classifications](https://oecd.ai/en/classification)
39
- - Ensure compatability with [NIST AI 200-1 NIST Trustworthy and Responsible AI](https://www.nist.gov/publications/ai-use-taxonomy-human-centered-approach)
40
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
9
  > [!IMPORTANT]
10
  > # MIR (Machine Intelligence Resource)
11
 
12
+ MIR is a naming standard, a proposed schema for AIGC/ML work.<br>
13
  In its current incarnation, it looks like this:
14
 
15
  > [!NOTE]
 
34
  - Efficient and reliable compatability checks
35
  - Organized hyperparameter management
36
 
 
 
 
37
 
38
+ > <details> <summary>Why not `diffusion`, `transformer`, `sgm`, `ldm`, `text`, hf.co folder-structure, (brand-specific trade word)</summary>
39
+ >
40
+ > - Exact frameworks (SGM/LDM/RectifiedFlow) includes too few
41
+ > - Diffusion/Transformer are too broad, share and overlap resources
42
+ > - Multimodal models complicate content terms (Text/Image/Vision/etc)
43
+ > - HF.CO names do all of this, inconsistent across folders/files
44
+ > - Impartiality
45
+ > </details>
46
+
47
+ > <details><summary>Why `unet`, `dit`, `lora` over alternatives</summary>
48
+ >
49
+ > - UNET/DiT are shared enough to be a genre but not too narrowly specific
50
+ > - Very similar technical process on this level
51
+ > - Functional and efficient for random lookups
52
+ > </details>
53
+
54
+ > <details><summary>Roadmap</summary>
55
+ >
56
+ > - Decide on `@` (like @8cfg for an indistinguishable 8 step lora that requires cfg)
57
+ > -- crucial spec element, or an optional, MIR app-determined feature?
58
+ > - Proof of concept generative model registry
59
+ > - Ensure compatability/integration/cross-pollenation with [OECD AI Classifications](https://oecd.ai/en/classification)
60
+ > - Ensure compatability/integration/cross-pollenation with [NIST AI 200-1 NIST Trustworthy and Responsible AI](https://www.nist.gov/publications/ai-use-taxonomy-human-centered-approach)
61
+ > </details>