- Joined
- Dec 29, 2017
- Messages
- 5,045 (1.99/day)
- Location
- Swansea, Wales
System Name | Silent |
---|---|
Processor | Ryzen 7800X3D @ 5.15ghz BCLK OC, TG AM5 High Performance Heatspreader |
Motherboard | ASUS ROG Strix X670E-I, chipset fans replaced with Noctua A14x25 G2 |
Cooling | Optimus Block, HWLabs Copper 240/40 + 240/30, D5/Res, 4x Noctua A12x25, 1x A14G2, Mayhems Ultra Pure |
Memory | 32 GB Dominator Platinum 6150 MT 26-36-36-48, 56.6ns AIDA, 2050 FCLK, 160 ns tRFC, active cooled |
Video Card(s) | RTX 3080 Ti Founders Edition, Conductonaut Extreme, 18 W/mK MinusPad Extreme, Corsair XG7 Waterblock |
Storage | Intel Optane DC P1600X 118 GB, Samsung 990 Pro 2 TB |
Display(s) | 32" 240 Hz 1440p Samsung G7, 31.5" 165 Hz 1440p LG NanoIPS Ultragear, MX900 dual gas VESA mount |
Case | Sliger SM570 CNC Aluminium 13-Litre, 3D printed feet, custom front, LINKUP Ultra PCIe 4.0 x16 white |
Audio Device(s) | Audeze Maxwell Ultraviolet w/upgrade pads & LCD headband, Galaxy Buds 3 Pro, Razer Nommo Pro |
Power Supply | SF750 Plat, full transparent custom cables, Sentinel Pro 1500 Online Double Conversion UPS w/Noctua |
Mouse | Razer Viper Pro V2 8 KHz Mercury White w/Tiger Ice Skates & Pulsar Supergrip tape |
Keyboard | Wooting 60HE+ module, TOFU-R CNC Alu/Brass, SS Prismcaps W+Jellykey, LekkerV2 mod, TLabs Leath/Suede |
Software | Windows 11 IoT Enterprise LTSC 24H2 |
Benchmark Scores | Legendary |
Where I can see hyperloop or the generic equivalent being useful is between towns and cities, to avoid flying. No more big airports taking space, just a next generation tube/underground equivalent, with much less noise and vibration, and much faster transit times, entry/egress points being more convenient. This could eliminate need for cars and planes, where you just have the London system of underground, but scaled up in distance and speed, commute by foot or bike at either end.The big concept / theory seems doable. But in terms of "will this survive a California Earthquake", you'd never draw just 3 pylons and call it a structural analysis of the concept.
When you consider the actual issue that California was worried about (ie: California Earthquakes), there's a level of analysis that requires more than like, 3-hours on a computer to figure out. (IE: I'd probably replicate that level of analysis within 3 hours, with the first 2 hours remembering how to use FEA programs and 1 hour to draw the thing). Its an incredibly shallow level of discussion / analysis in that document. Incredibly shallow, relying upon nearly the default materials/default settings of the program.
-----
Thanks to playing traffic simulator games (IE, OpenTTD), I've also become a bit better with throughput vs latency vs traffic when it comes down to analyzing mass transit proposals. Single-car designs (like Philadelphia TRAMS) can work, but you lose throughput significantly. Since throughput / people moved per hour is lower, such a proposal is seemingly designed as a boutique option, rather than a serious mass transit solution. I dunno how much traffic the SF to LA corridor has (I'm no civil engineer), but I have my doubts that Hyperloop, with a low throughput design as discussed, would make a dent in that traffic.
I admit this is video-game knowledge instead of real life knowledge though. But I can't imagine that fundamental laws of throughput/latency would change between real life and simulations (at least, from the simplistic model of throughput vs latency). That is to say: a singular train of eight cars will have fewer delays in the aggregate than 8x single-cars individually stopping at each location. You can't beat the fundamental traffic problem of throughput vs latency (individual pods are better latency, but far worse throughput).
Obviously for earthquake zones anything underground is problematic and your analysis is correct there. I'm in the middle re ol' Musky, he is a salesman, but he also stimulated great advances, quickly.