<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
	<id>https://sudoroom.org/mediawiki/index.php?action=history&amp;feed=atom&amp;title=Morning_math%2FModels</id>
	<title>Morning math/Models - Revision history</title>
	<link rel="self" type="application/atom+xml" href="https://sudoroom.org/mediawiki/index.php?action=history&amp;feed=atom&amp;title=Morning_math%2FModels"/>
	<link rel="alternate" type="text/html" href="https://sudoroom.org/mediawiki/index.php?title=Morning_math/Models&amp;action=history"/>
	<updated>2026-04-04T10:03:44Z</updated>
	<subtitle>Revision history for this page on the wiki</subtitle>
	<generator>MediaWiki 1.37.2</generator>
	<entry>
		<id>https://sudoroom.org/mediawiki/index.php?title=Morning_math/Models&amp;diff=1445&amp;oldid=prev</id>
		<title>50.0.83.116: creates page</title>
		<link rel="alternate" type="text/html" href="https://sudoroom.org/mediawiki/index.php?title=Morning_math/Models&amp;diff=1445&amp;oldid=prev"/>
		<updated>2012-12-18T18:12:59Z</updated>

		<summary type="html">&lt;p&gt;creates page&lt;/p&gt;
&lt;p&gt;&lt;b&gt;New page&lt;/b&gt;&lt;/p&gt;&lt;div&gt;A mathematical model can be very simple or very complex. The goal is to represent a system or process using precise definitions and mathematical relationships. One way to create a model is to simply start building it, acknowledging it won't be perfect, but trying to improve the model along the way. Eventually you should arrive at a basic (fairly simple) model, which you can then make more complex (and perhaps more accurate) by elaborating in areas that previously were glossed over.&lt;br /&gt;
&lt;br /&gt;
For instance, if I want to represent amount of daylight in a single day, one of the simplest models might be:&lt;br /&gt;
&lt;br /&gt;
* For any given day D, some percentage of that day occurs in which there is measurable daylight L. &lt;br /&gt;
&lt;br /&gt;
However, I can improve this model and make it more complicated by:&lt;br /&gt;
&lt;br /&gt;
* Measuring daylight L as hours, minutes, seconds, milliseconds (or similarly as some percentage up to a particular decimal point e.g. 49.255%) of some day.&lt;br /&gt;
* Adding new variables, such as a geolocation--G&amp;lt;sub&amp;gt;1&amp;lt;/sub&amp;gt; longitude and G&amp;lt;sub&amp;gt;2&amp;lt;/sub&amp;gt; latitude, since daylight is a function of where on the earth measurement is taken. Or, allowing daylight to be more than a percentage, represented by an additional variable for luminosity U (imagine clouds reducing the impact of daylight). &lt;br /&gt;
&lt;br /&gt;
However, perhaps some of the complications are not relevant given the context, so one may want to simplify the model to simply be:&lt;br /&gt;
&lt;br /&gt;
* Daylight L for any given day D is a function of location only (G&amp;lt;sub&amp;gt;1&amp;lt;/sub&amp;gt; longitude and G&amp;lt;sub&amp;gt;2&amp;lt;/sub&amp;gt; latitude). Now, if we construct a look-up table for daylight at any given geolocation, we'd be able to find '''L(G&amp;lt;sub&amp;gt;1&amp;lt;/sub&amp;gt;, G&amp;lt;sub&amp;gt;2&amp;lt;/sub&amp;gt;) = some # of seconds per day D'''.&lt;/div&gt;</summary>
		<author><name>50.0.83.116</name></author>
	</entry>
</feed>