<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
	<id>https://qqpipi.com//api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Timothy-gonzalez55</id>
	<title>Qqpipi.com - User contributions [en]</title>
	<link rel="self" type="application/atom+xml" href="https://qqpipi.com//api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Timothy-gonzalez55"/>
	<link rel="alternate" type="text/html" href="https://qqpipi.com//index.php/Special:Contributions/Timothy-gonzalez55"/>
	<updated>2026-11-06T18:27:53Z</updated>
	<subtitle>User contributions</subtitle>
	<generator>MediaWiki 1.42.3</generator>
	<entry>
		<id>https://qqpipi.com//index.php?title=How_Do_I_Choose_Between_a_Discrete_Model_and_a_Continuous_Model%3F&amp;diff=2543117</id>
		<title>How Do I Choose Between a Discrete Model and a Continuous Model?</title>
		<link rel="alternate" type="text/html" href="https://qqpipi.com//index.php?title=How_Do_I_Choose_Between_a_Discrete_Model_and_a_Continuous_Model%3F&amp;diff=2543117"/>
		<updated>2026-11-05T18:49:34Z</updated>

		<summary type="html">&lt;p&gt;Timothy-gonzalez55: Created page with &amp;quot;&amp;lt;html&amp;gt;&amp;lt;p&amp;gt; Choosing between a discrete and a continuous model is not just a question of which graph looks smoother. It is a question about what is being recorded, when it is recorded, and what the model is supposed to help you decide. A poor model can make a correct calculation answer the wrong question. A good model makes the meaning of the data—and its limits—clear.&amp;lt;/p&amp;gt; &amp;lt;p&amp;gt; Before doing any math, ask: &amp;lt;strong&amp;gt; What are the units?&amp;lt;/strong&amp;gt; Then ask what quantity thos...&amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;html&amp;gt;&amp;lt;p&amp;gt; Choosing between a discrete and a continuous model is not just a question of which graph looks smoother. It is a question about what is being recorded, when it is recorded, and what the model is supposed to help you decide. A poor model can make a correct calculation answer the wrong question. A good model makes the meaning of the data—and its limits—clear.&amp;lt;/p&amp;gt; &amp;lt;p&amp;gt; Before doing any math, ask: &amp;lt;strong&amp;gt; What are the units?&amp;lt;/strong&amp;gt; Then ask what quantity those units describe. Are you counting packages in a warehouse, measuring water in a tank, tracking a balance, or reporting a delivery rate? Units help distinguish a total from a rate, while the way a quantity is recorded helps determine whether a discrete or continuous model makes sense.&amp;lt;/p&amp;gt; &amp;lt;h2&amp;gt; The short answer&amp;lt;/h2&amp;gt; &amp;lt;p&amp;gt; Use a &amp;lt;strong&amp;gt; discrete model&amp;lt;/strong&amp;gt; when the quantity is counted or recorded at separate steps or events: packages received each hour, a balance at the end of each month, or the number of orders placed on each day. Use a &amp;lt;strong&amp;gt; continuous model&amp;lt;/strong&amp;gt; when the quantity is meaningfully treated as changing throughout an interval: the temperature in a room, the distance traveled over time, or the amount of fuel in a tank.&amp;lt;/p&amp;gt;&amp;lt;p&amp;gt; &amp;lt;img  src=&amp;quot;https://images.pexels.com/photos/12843338/pexels-photo-12843338.jpeg?auto=compress&amp;amp;cs=tinysrgb&amp;amp;h=650&amp;amp;w=940&amp;quot; style=&amp;quot;max-width:500px;height:auto;&amp;quot; &amp;gt;&amp;lt;/img&amp;gt;&amp;lt;/p&amp;gt; &amp;lt;p&amp;gt; That distinction is a useful starting point—not an automatic rule. Some processes change continuously but are only measured at discrete times. Some data are recorded continuously but are best summarized in daily or monthly steps. The right choice depends on the purpose of the model and the details the data actually support.&amp;lt;/p&amp;gt; &amp;lt;h2&amp;gt; First, say what is being measured&amp;lt;/h2&amp;gt; &amp;lt;p&amp;gt; Before selecting a model, rewrite the situation as one clean sentence that names the quantity and its time reference. For example: “The inventory total is the number of unopened cases in the warehouse at the close of each business day.” This sentence tells us what is counted, what the unit is, and when each record is taken.&amp;lt;/p&amp;gt; &amp;lt;p&amp;gt; That is much more informative than “inventory over time.” The phrase “inventory over time” leaves several important questions unanswered. Does inventory mean cases on hand, cases received, or cases shipped? Is the total measured at opening or closing? Are the records hourly, daily, or monthly?&amp;lt;/p&amp;gt;&amp;lt;p&amp;gt; &amp;lt;img  src=&amp;quot;https://images.pexels.com/photos/22690748/pexels-photo-22690748.jpeg?auto=compress&amp;amp;cs=tinysrgb&amp;amp;h=650&amp;amp;w=940&amp;quot; style=&amp;quot;max-width:500px;height:auto;&amp;quot; &amp;gt;&amp;lt;/img&amp;gt;&amp;lt;/p&amp;gt; &amp;lt;ul&amp;gt;  &amp;lt;li&amp;gt; &amp;lt;strong&amp;gt; Recorded quantity:&amp;lt;/strong&amp;gt; What value is being counted, measured, or calculated?&amp;lt;/li&amp;gt; &amp;lt;li&amp;gt; &amp;lt;strong&amp;gt; Units:&amp;lt;/strong&amp;gt; Is the quantity measured in cases, dollars, liters, miles, or something else?&amp;lt;/li&amp;gt; &amp;lt;li&amp;gt; &amp;lt;strong&amp;gt; Start time:&amp;lt;/strong&amp;gt; What time is assigned to the first value? Is it the beginning or end of a reporting period?&amp;lt;/li&amp;gt; &amp;lt;li&amp;gt; &amp;lt;strong&amp;gt; Time step:&amp;lt;/strong&amp;gt; Are observations separated by minutes, hours, days, or months?&amp;lt;/li&amp;gt; &amp;lt;li&amp;gt; &amp;lt;strong&amp;gt; Purpose:&amp;lt;/strong&amp;gt; Are you trying to report a total, estimate a rate, forecast a future value, or compare periods?&amp;lt;/li&amp;gt; &amp;lt;/ul&amp;gt; &amp;lt;p&amp;gt; “Start time” deserves special attention. If a report says a balance is $8,400 in January, that could mean the balance on January 1, the balance on January 31, or the average balance during January. Those are different quantities, and a model should not quietly treat them as interchangeable.&amp;lt;/p&amp;gt; &amp;lt;h2&amp;gt; Discrete models: values at separate steps&amp;lt;/h2&amp;gt; &amp;lt;p&amp;gt; A discrete model describes values at distinct steps, often numbered with integers. If \(I_n\) is the inventory at the close of day \(n\), then the sequence \(I_0, I_1, I_2, \ldots\) could represent the recorded inventory at the close of each day. The subscript identifies a step, not every instant between steps.&amp;lt;/p&amp;gt; &amp;lt;p&amp;gt; Discrete models are a natural fit for quantities such as:&amp;lt;/p&amp;gt; &amp;lt;ul&amp;gt;  &amp;lt;li&amp;gt; the number of packages received in each shift;&amp;lt;/li&amp;gt; &amp;lt;li&amp;gt; the number of customers served each day;&amp;lt;/li&amp;gt; &amp;lt;li&amp;gt; a loan balance recorded at each month-end;&amp;lt;/li&amp;gt; &amp;lt;li&amp;gt; the number of units in stock after each delivery;&amp;lt;/li&amp;gt; &amp;lt;li&amp;gt; the total distance recorded at the end of each trip segment.&amp;lt;/li&amp;gt; &amp;lt;/ul&amp;gt; &amp;lt;p&amp;gt; A step graph can be helpful when values remain in effect until the next recorded event or update. If inventory is reported at the end of each day, a step graph emphasizes the daily records without suggesting that someone measured inventory at every instant. When deliveries and shipments cause sudden changes, drawing steps on purpose is often more honest than connecting every point with a smooth line.&amp;lt;/p&amp;gt; &amp;lt;p&amp;gt; For example, suppose a warehouse starts with 120 cases. A delivery adds 40 cases at 10 a.m., and a shipment removes 25 at 2 p.m. The inventory changes in jumps. A model based on event times might show a step from 120 to 160, then from 160 to 135. A straight-line connection would imply that cases arrived or left gradually, which is not what happened.&amp;lt;/p&amp;gt; &amp;lt;h2&amp;gt; Continuous models: values throughout an interval&amp;lt;/h2&amp;gt; &amp;lt;p&amp;gt; A continuous model treats a quantity as having a value at every time in an interval. If \(T(t)\) represents the temperature in a room \(t\) hours after a heater is switched on, a continuous model can describe estimated temperature between readings as well as at the recorded times.&amp;lt;/p&amp;gt; &amp;lt;p&amp;gt; Continuous models are useful when gradual change is a meaningful approximation. Examples include the height of water in a tank as it drains, the distance traveled by a vehicle, and the value of an investment under a specified growth model. In each case, the model can estimate values between observations—but those estimates rely on assumptions about how change occurs.&amp;lt;/p&amp;gt; &amp;lt;p&amp;gt; A smooth curve does not prove that the real process was smooth. A sensor may record temperature every five minutes even though the room’s temperature changes between readings. The observations are discrete, while a continuous model may still be useful for estimating the underlying process. It is important to distinguish &amp;lt;strong&amp;gt; how often data are recorded&amp;lt;/strong&amp;gt; from &amp;lt;strong&amp;gt; how the process is modeled&amp;lt;/strong&amp;gt;.&amp;lt;/p&amp;gt; &amp;lt;h2&amp;gt; Totals and rates answer different questions&amp;lt;/h2&amp;gt; &amp;lt;p&amp;gt; One of the most common mistakes in interpreting charts is confusing a total with a rate. A total answers “how much altogether?” A rate answers “how much per unit of time, distance, or some other quantity?” They are related, but they are not the same thing.&amp;lt;/p&amp;gt;     Quantity  Example  Units  Question answered     Total shipped 240 packages packages How many packages were shipped?   Average shipping rate 60 packages per hour packages/hour How quickly were packages shipped on average?   Account balance $2,500 dollars How much money is in the account?   Change in balance per month $125 per month dollars/month How quickly did the balance change?    &amp;lt;p&amp;gt; If a dashboard shows 240 packages shipped during a four-hour shift, the average shipping rate is \(240 \div 4 = 60\) packages per hour. The total is still 240 packages. Calling the total “60 packages” would be wrong; calling the rate “240 packages per hour” would also be wrong. The units tell us which question each number answers.&amp;lt;/p&amp;gt; &amp;lt;p&amp;gt; In a continuous model, the derivative often represents an instantaneous rate of change. In a discrete model, a difference between successive values represents change over a step. These ideas are related, but they should not be described as the same measurement. The difference \(I_n+1-I_n\) has units of cases; dividing by the time step gives an average rate in cases per day.&amp;lt;/p&amp;gt; &amp;lt;h2&amp;gt; Intervals matter for average rate of change&amp;lt;/h2&amp;gt; &amp;lt;p&amp;gt; An average rate of change depends on both endpoint values and the interval between them. If a balance changes from \(B(t_1)\) to \(B(t_2)\), the average rate is&amp;lt;/p&amp;gt; &amp;lt;p&amp;gt; \&amp;amp;#91; \fracB(t_2)-B(t_1)t_2-t_1. \&amp;amp;#93;&amp;lt;/p&amp;gt; &amp;lt;p&amp;gt; The numerator describes the change in balance. The denominator describes the length of the interval. If the balance is measured in dollars and time in months, the result is in dollars per month.&amp;lt;/p&amp;gt; &amp;lt;p&amp;gt; For example, suppose a balance rises from $1,200 to $1,500 over three months. The change is $300, and the average rate is \(300 \div 3 = 100\) dollars per month. That does not mean the balance increased by exactly $100 in each month. It means the average change across the full three-month interval was $100 per month.&amp;lt;/p&amp;gt; &amp;lt;p&amp;gt; The interval matters even more when the data contain jumps. If a shipment is logged at 9:00 a.m. and another at 11:00 a.m., the average rate over those two hours can be calculated. But it does not tell you exactly when packages moved, or whether activity was steady. If the timestamps are uneven, using the number of records as though each represented the same amount of time can produce a misleading rate.&amp;lt;/p&amp;gt; &amp;lt;p&amp;gt; Be explicit about time units, too. A rate of 30 packages per hour is not the same as 30 packages per minute. If a report mixes hours and minutes, convert them before calculating. For example, 90 minutes is 1.5 hours, not 90 hours.&amp;lt;/p&amp;gt; &amp;lt;h2&amp;gt; What details matter for model selection?&amp;lt;/h2&amp;gt; &amp;lt;p&amp;gt; When you are deciding between a discrete vs continuous model, use the following checks. They turn model selection into a practical question about evidence and purpose, rather than a guess based on the appearance of a chart.&amp;lt;/p&amp;gt; &amp;lt;ol&amp;gt;  &amp;lt;li&amp;gt; &amp;lt;strong&amp;gt; Identify the quantity.&amp;lt;/strong&amp;gt; Write down exactly what each value represents. Avoid broad labels such as “sales” if the data could mean orders, dollars, or units sold.&amp;lt;/li&amp;gt; &amp;lt;li&amp;gt; &amp;lt;strong&amp;gt; State the units.&amp;lt;/strong&amp;gt; Label both axes. A time axis might use days or hours; a vertical axis might use dollars, liters, or customers. A rate needs compound units, such as dollars per month.&amp;lt;/li&amp;gt; &amp;lt;li&amp;gt; &amp;lt;strong&amp;gt; Set the time reference.&amp;lt;/strong&amp;gt; Say when the first observation occurs and whether a value describes a moment, a period total, or a period average.&amp;lt;/li&amp;gt; &amp;lt;li&amp;gt; &amp;lt;strong&amp;gt; Check the recording schedule.&amp;lt;/strong&amp;gt; Are observations taken at regular intervals, or only when events occur? Are any timestamps missing?&amp;lt;/li&amp;gt; &amp;lt;li&amp;gt; &amp;lt;strong&amp;gt; Consider how the process changes.&amp;lt;/strong&amp;gt; Does it move gradually, or does it jump when a delivery, payment, or transaction occurs?&amp;lt;/li&amp;gt; &amp;lt;li&amp;gt; &amp;lt;strong&amp;gt; Match the model to the purpose.&amp;lt;/strong&amp;gt; A step graph may be right for reporting actual counts. A continuous curve may be useful for estimating an underlying trend between measurements.&amp;lt;/li&amp;gt; &amp;lt;li&amp;gt; &amp;lt;strong&amp;gt; State what is estimated.&amp;lt;/strong&amp;gt; If the model fills in values between recorded times, make clear that those values are estimates, not direct observations.&amp;lt;/li&amp;gt; &amp;lt;/ol&amp;gt; &amp;lt;h2&amp;gt; A quick example: a monthly account balance&amp;lt;/h2&amp;gt; &amp;lt;p&amp;gt; Suppose a business records its account balance at the end of each month. First, rewrite the situation in one clean sentence: “The recorded quantity is the number of dollars in the account at each month-end, starting on January 31.” The units are dollars, and the records are discrete monthly observations.&amp;lt;/p&amp;gt; &amp;lt;p&amp;gt; If the goal is to display the recorded balances, a discrete plot or point graph is appropriate. Connecting the points with a &amp;lt;a href=&amp;quot;https://activecalculus.org/author/Running-Totals-Rates-of-Change&amp;quot;&amp;gt;https://activecalculus.org/author/Running-Totals-Rates-of-Change&amp;lt;/a&amp;gt; line can help show a broad trend, but viewers may interpret the line as estimated values between months. If interest is being added continuously under a stated assumption, a continuous model could be useful for estimating the balance at an arbitrary date. The model choice depends on whether the question is about recorded month-end totals or estimated behavior between those dates.&amp;lt;/p&amp;gt;&amp;lt;p&amp;gt; &amp;lt;iframe  src=&amp;quot;https://www.youtube.com/embed/zklPjhexTyI&amp;quot; width=&amp;quot;560&amp;quot; height=&amp;quot;315&amp;quot; style=&amp;quot;border: none;&amp;quot; allowfullscreen=&amp;quot;&amp;quot; &amp;gt;&amp;lt;/iframe&amp;gt;&amp;lt;/p&amp;gt; &amp;lt;p&amp;gt; If the balance rises from $10,000 at the end of January to $10,600 at the end of April, the change is $600 over three months. The average rate of change is $200 per month. That is an average across the interval—not necessarily the change in each individual month, and not a new balance total.&amp;lt;/p&amp;gt; &amp;lt;h2&amp;gt; Using MathJax and Runestone thoughtfully&amp;lt;/h2&amp;gt; &amp;lt;p&amp;gt; MathJax can render mathematical notation in web pages, including expressions such as \(\fracB(t_2)-B(t_1)t_2-t_1\). Clear notation is useful, but equations should support the explanation rather than replace it. Pair formulas with words that name the quantity, interval, and units. For instance, explain that a difference quotient measures average change in dollars per month when the balance is measured in dollars and time in months.&amp;lt;/p&amp;gt; &amp;lt;p&amp;gt; Runestone is an interactive publishing platform that can support learning through embedded questions, activities, and feedback. A lesson on model selection could ask learners to classify examples, label graph axes, or decide whether a step graph or smooth curve fits a scenario. The most valuable prompts ask learners to explain what details matter—not merely choose “discrete” or “continuous.”&amp;lt;/p&amp;gt; &amp;lt;h2&amp;gt; A practical rule to remember&amp;lt;/h2&amp;gt; &amp;lt;p&amp;gt; Choose a discrete model when the meaningful values are recorded at separate steps or events, and a continuous model when estimating values throughout an interval is useful and defensible. Then check that the model preserves the meaning of the data. Name the recorded quantity, identify the start time, specify the interval, distinguish totals from rates, and label every unit.&amp;lt;/p&amp;gt; &amp;lt;p&amp;gt; If you are unsure, begin with the observations as they were actually recorded. Show discrete points or steps, especially when events happen in jumps. Add a continuous curve only when it serves a clear purpose, and explain what it assumes between observations. That approach keeps the chart honest—and makes the answer easier to use.&amp;lt;/p&amp;gt;&amp;lt;/html&amp;gt;&lt;/div&gt;</summary>
		<author><name>Timothy-gonzalez55</name></author>
	</entry>
</feed>