Check out my first novel, midnight's simulacra!

Counterforce: Difference between revisions

From dankwiki
(Created page with "Counterforce is my project for next-level computer cooling, management, modeling, and visualization, borne out of a few years spent watercooling. My first nascent writeup was posted to reddit's [https://www.reddit.com/r/watercooling/comments/wr667q/automated_modeling_of_cooling_system/ r/watercooling] on 2022-08-18. I want to bring Linux to the same levels of hardware awareness long available to Windows users through tools like HWInfo...and then wildly surpass those leve...")
 
No edit summary
Line 1: Line 1:
Counterforce is my project for next-level computer cooling, management, modeling, and visualization, borne out of a few years spent watercooling. My first nascent writeup was posted to reddit's [https://www.reddit.com/r/watercooling/comments/wr667q/automated_modeling_of_cooling_system/ r/watercooling] on 2022-08-18. I want to bring Linux to the same levels of hardware awareness long available to Windows users through tools like HWInfo...and then wildly surpass those levels. The ambitious end goal is to <i>automatically model the physical cooling system, and associate it with sensors without human interaction.</i> I expect this project to require several years, along with some custom hardware, and it might prove infeasible for arbitrary builds.
Counterforce is my project for next-level computer cooling, management, modeling, and visualization, borne out of a few years spent watercooling. My first nascent writeup was posted to reddit's [https://www.reddit.com/r/watercooling/comments/wr667q/automated_modeling_of_cooling_system/ r/watercooling] on 2022-08-18. I want to bring Linux to the same levels of hardware awareness long available to Windows users through tools like HWInfo...and then wildly surpass those levels. The ambitious end goal is to <i>automatically model the physical cooling system, and associate it with sensors without human interaction.</i> I expect this project to require several years, along with some custom hardware, and it might prove infeasible for arbitrary builds.


The core principles of this effort include:
* Users ought not need to know (or pretend to know) the relationships between hardware control and cooling effect.
* Control of audible noise is almost as important as control of cooling effect.
* Changes within and without the system ought be integrated into control in realtime, and without user intervention.
* Quality visualization is critical for understanding the generation and elimination of heat.
* Closed source has no place in the coolant loop.


==Stage I: Linux sensor/control support==
==Stage II: Data discovery and visualization==
==Stage III: Volume-based coolant control==
==Stage IV: Intelligent coolant control==
==Stage V: System discovery and visualization==


[[CATEGORY: Hardware]]
[[CATEGORY: Hardware]]
[[CATEGORY: Projects]]
[[CATEGORY: Projects]]

Revision as of 02:47, 19 August 2022

Counterforce is my project for next-level computer cooling, management, modeling, and visualization, borne out of a few years spent watercooling. My first nascent writeup was posted to reddit's r/watercooling on 2022-08-18. I want to bring Linux to the same levels of hardware awareness long available to Windows users through tools like HWInfo...and then wildly surpass those levels. The ambitious end goal is to automatically model the physical cooling system, and associate it with sensors without human interaction. I expect this project to require several years, along with some custom hardware, and it might prove infeasible for arbitrary builds.

The core principles of this effort include:

  • Users ought not need to know (or pretend to know) the relationships between hardware control and cooling effect.
  • Control of audible noise is almost as important as control of cooling effect.
  • Changes within and without the system ought be integrated into control in realtime, and without user intervention.
  • Quality visualization is critical for understanding the generation and elimination of heat.
  • Closed source has no place in the coolant loop.

Stage I: Linux sensor/control support

Stage II: Data discovery and visualization

Stage III: Volume-based coolant control

Stage IV: Intelligent coolant control

Stage V: System discovery and visualization