3 ms·
Assuming you want to know how the tube works, as a passenger, independently of other systems, then yes. But if you're building a grand unified model of how Lon
by pbhjpbhj 8y ago
Assuming you want to know how the tube works, as a passenger, independently of other systems, then yes.
But if you're building a grand unified model of how London works then not only do you want to be able to abstract certain facets, you also want to be able to combine the models those abstractions create with data points to build a more complex systemic model. You want to look at where the stations are in relation to others, how the different transport networks link, what happens when a tube-train stops - how does the effect ripple through the system and alter what time a particular Pret-a-manger have to restock the sandwiches.
At that point the abstraction in to a simplified system that only describes the tube is useless you need to combine the abstractions to model the entire system - and you may be able to get there, except your model missed out sunspot activity and a bus-driver turned the wrong way because their GPS was marginally out and the Pret-a-manger manager missed the start of the shift and now you have to eat Cheese instead of Mexican chicken.
In short you want your abstraction to be able to construct a model that is as close as necessary for the purpose to the "photorealistic, lifelike copy" of whatever it is you're seeking to predict. If you only wish to predict how many stops you'll need to stay on the tube for then a simple tube map suffices. If you want to predict airflow through the tube system and how it affects heat exchange then a more complex model will be needed, with different abstractions (preserving length of tunnels for example).
If you want to predict everything that it's possible to predict ...
[Disclaimer I've no idea what Pret's menu is.]