Project talk:Data Dictionary: Difference between revisions
From Step Mods | Change The Game
No edit summary |
No edit summary |
||
Line 14: | Line 14: | ||
* '''ByteDiff''' - This would hold the byte diff from the log output. | * '''ByteDiff''' - This would hold the byte diff from the log output. | ||
* '''VramDiff''' - This would contain the resulting VRAM change of the pre/post optimized versions. | * '''VramDiff''' - This would contain the resulting VRAM change of the pre/post optimized versions. | ||
~[[User:z929669|z929669]][[File:Ixian_Insignia.png|30px|link=User:z929669]][[User talk:z929669|Talk]] 02:44, December 17, 2012 (UTC) | |||
: ''Section'' is already declared as a property under Template:Mod. The distinction between Mod and ModAttributes is that Mod is for basic info such as the mod's name, section, NexusID, etc. while ModAttributes is based around the ticket/performance data results and will be the kind of stuff that needs some amount of discussion/consensus before declaring. | |||
: All of those sub-properties will be great to have. The problematic one will be ''VramDiff'' since it will likely be different depending on the rig. | |||
: ~[[User:Farlo|Farlo]][[File:User Farlo Sig.png|19px|link=User:Farlo]]<small>[[User talk:Farlo|Talk]]</small> 04:22, December 17, 2012 (UTC) | |||
---- | ---- | ||
Line 25: | Line 28: | ||
: - Broke out elements of Template:ModTest into Template:PerformanceImpact. Reason being that this is an important multi-faceted variable to track in and of itself. I see this being the info that basically qualifes the Property, 'AffectsPerformance' (sub-properties using 'AffectsPerformance via Internal Objects). Still thinking about designing a simple way to roll up testing results (including performance data) with SystemSpecs into a single form if possible. | : - Broke out elements of Template:ModTest into Template:PerformanceImpact. Reason being that this is an important multi-faceted variable to track in and of itself. I see this being the info that basically qualifes the Property, 'AffectsPerformance' (sub-properties using 'AffectsPerformance via Internal Objects). Still thinking about designing a simple way to roll up testing results (including performance data) with SystemSpecs into a single form if possible. | ||
:~[[User:z929669|z929669]][[File:Ixian_Insignia.png|30px|link=User:z929669]][[User talk:z929669|Talk]] 07:56, November 5, 2012 (UTC) | :~[[User:z929669|z929669]][[File:Ixian_Insignia.png|30px|link=User:z929669]][[User talk:z929669|Talk]] 07:56, November 5, 2012 (UTC) | ||
:: Associating SystemSpecs with the performance data shouldn't be too difficult. The form will grab the user's name and simply apply their SystemSpecs declarations to the report itself. Basically: "TestReport#34/CPUProperty" = "User:Farlo/CPUProperty". Thus we end up with the reports having a full set of specs themselves which means we don't have to include anything about the users while querying them and they will remain static even if the user updates their specs. | |||
---- | ---- | ||
: | : {{fc|pink|{{fs|1.2em|Need to not turn headings into wiki text, as this breaks "right-click to edit" functionality!}} }} | ||
:~[[User:z929669|z929669]][[File:Ixian_Insignia.png|30px|link=User:z929669]][[User talk:z929669|Talk]] 06:23, November 21, 2012 (UTC) | :~[[User:z929669|z929669]][[File:Ixian_Insignia.png|30px|link=User:z929669]][[User talk:z929669|Talk]] 06:23, November 21, 2012 (UTC) | ||