CameronCarroll

*Some nonsense I got Deepseek to write while I was supposed to be studying threat modeling for work...*

In the neon-veined heart of the Silicon Spires, a city where skyscrapers of glass and crystalline data servers pierced clouds threaded with ley lines, Elara’s world hummed with dual currents. By day, she debugged code in the vaulted halls of the AstraLoom Foundry, a guild of technomancers who wove artificial intelligence into tapestries of light. By night, she wandered the Undercode District, where black-market spellware vendors hawked bootleg hexes disguised as NFT charms, and data streams pooled in the gutters like liquid starlight. It was here, in the flicker between realms, that her magic first erupted—unbidden, undeniable.

During a routine firewall audit, her fingers brushed a corrupted server node. Instead of sparks, syllables spilled out—ancient, glitching incantations that rearranged the node’s code into a living cipher. The server sang, its malware purged into a flock of iridescent data-moths. Ma

CameronCarroll

Title: Threat Modeling the Sentinel of Synthia Colony

Genre: Space Sci-Fi / Cybersecurity Thriller
1. Setting & Context

    Year: 2145, Location: Synthia Colony, Mars.
    Core Tech: Central Life-Support System (CLSS) integrating medical devices (bio-monitors, nanobot injectors, AI-driven surgical units).
    Dependency: Colony survival hinges on secure, networked medical infrastructure.

2. Protagonist & Inciting Incident

CameronCarroll

Title: Threat Modeling the Sentinel of Synthia Colony

Genre: Space Sci-Fi / Cybersecurity Thriller
1. Setting & Context

    Year: 2145, Location: Synthia Colony, Mars.
    Core Tech: Central Life-Support System (CLSS) integrating medical devices (bio-monitors, nanobot injectors, AI-driven surgical units).
    Dependency: Colony survival hinges on secure, networked medical infrastructure.

2. Protagonist & Inciting Incident

CameronCarroll

ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQDoHeGpOjJi2n/Z51Msv8lPGFfgStFSjZ4ZNPkKg/BcAw9B/xNe8j8kuML8TdFyJTy9g6KlVM4an7U2kdSCtQoMRX0uFSPyrX8GwmsY3G7x2P7mHBDgprIJhOpM5HEGozgiWD3u9LohgAIVe9sDDq1RFF64ICs4/bHQ6z6Gxg0FkFciTuCd3S/mUERd3ZexoBHlJz9HmeLYLv2gr3elC7cCpEtSfAsus6QguUh8HFZ7Kh5yRLJX2ra5QspygGqxFLKkD3bGhpbVC2TYlfMRdFCwQd5YUC/5lHMoJv5vmdFLyOC01SUva3Af32AHV2JSSs89XdIL85V+llee7Ob89GW7 cameron@Deadmines

CameronCarroll

SAE Technical Standards included in the CDS Rules

A3.11 SAE Technical Standards Access
A cooperative program of SAE’s Education Board and Technical Standards Board is making some
of SAE’s Technical Standards available to teams registered for any North American CDS
competition at no cost. The Technical Standards referenced in the Collegiate Design Series rules,
along with other standards with reference value, will be accessible online to registered teams, team
members and faculty advisors. To access the standards (1) your team must be registered for a
competition in North America and (2) the individual team member or faculty advisor wanting
access must be linked to the team in SAE’s system.

CameronCarroll

EV4.3 Grounding
EV4.3.1 All electrically conductive parts of the vehicle (e.g. parts made of steel, (anodized) aluminum, any
other metal parts, etc.) which are within 100mm of any tractive system or GLV component, and any
driver harness mounting points, seat mounting points and driver controls must have a resistance below
300 mOhms (measured with a current of 1A) to GLV system ground.
EV4.3.2 All parts of the vehicle which may become electrically conductive (e.g. completely coated metal parts,
carbon fiber parts, etc.) which are within 100mm of any tractive system or GLV component, must
have a resistance below 5 Ohm to GLV system ground.
EV4.3.3 Electrical conductivity of any part may be tested by checking any point which is likely to be
conductive, for example the driver's harness attachment bolt, but where no convenient conductive

CameronCarroll

== Design ==
* Compiled possible solutions for tradeoff analysis, building group knowledge of sensors and microcontrollers.
* Uncovering unknown components to the problem forced late redesign in system architecture. (Naive solution --> CPLD central control --> PCB control board)
* Design settled on a central PCB containing controls circuits, connected directly to vehicle sensors and switches.
* Some unexpected or misunderstood issues: Latching/reset button circuits, precharge/discharge circuits, galvanic isolation between HV and LV, safety interlocks
* Flowcharting/pseudocode for microcontroller and data-acquisition procedures before receiving devices

== Analysis ==
* Tradeoff analysis with decision matrices to select the many sensors, buttons, cables and connectors.
* RC-circuit discharge-time versus power-dissipation (for precharge/discharging of controller capacitors)

CameronCarroll

% Calculations for ME 241 Lab 6: Tensile Testing
% Group 2, December 12, Fall 2016

clear;
clc;

F_al = [0
181.1
362.2
543.3

CameronCarroll

#Tips for calculating phasor quantities using the 50g:

## Adding ->V2, RECT and CYLIN to soft menu

* We often need to convert between rectangular and polar form. Lets add these commands to the CUSTOM softmenu.
* V2 builds a two-dimensional vector using the first two stack values and builds in polar/rectangular depending on mode.
* RECT and CYLIN don't convert the first stack value as I thought they did, but instead set the coordinate mode.
* [Source from HP Forum](http://h30499.www3.hp.com/t5/Calculators/A-Simple-Way-to-Assign-Menu-Commands-with-HP50g/td-p/1162495) 
* [white] [mode=>custom] # to open custom softmenu
* {->V2 RECT CYLIN} [enter] MENU [enter] # caps values can be fetched from the [CAT]alog

CameronCarroll

mm_Pb = 207.2;% 82
mm_H = 1.008;% 1
mm_He = 4.003;% 2
mm_Li = 6.941;% 3
mm_Be = 9.012;% 4
mm_C = 12.01; % 6
mm_N = 14.007; % 7
mm_O = 16; % 8
mm_F = 18.998; % 9
mm_Ne = 20.18; % 10