sxli7eq08c
    • Create new note
    • Create a note from template
      • Sharing URL Link copied
      • /edit
      • View mode
        • Edit mode
        • View mode
        • Book mode
        • Slide mode
        Edit mode View mode Book mode Slide mode
      • Customize slides
      • Note Permission
      • Read
        • Only me
        • Signed-in users
        • Everyone
        Only me Signed-in users Everyone
      • Write
        • Only me
        • Signed-in users
        • Everyone
        Only me Signed-in users Everyone
    • Invite by email
      Invitee

      This note has no invitees

    • Publish Note

      Share your work with the world Congratulations! 🎉 Your note is out in the world Publish Note No publishing access yet

      Your note will be visible on your profile and discoverable by anyone.
      Your note is now live.
      This note is visible on your profile and discoverable online.
      Everyone on the web can find and read all notes of this public team.

      Your account was recently created. Publishing will be available soon, allowing you to share notes on your public page and in search results.

      Your team account was recently created. Publishing will be available soon, allowing you to share notes on your public page and in search results.

      Explore these features while you wait
      Complete general settings
      Bookmark and like published notes
      Write a few more notes
      Complete general settings
      Write a few more notes
      See published notes
      Unpublish note
      Please check the box to agree to the Community Guidelines.
      View profile
    • Commenting
      Permission
      Disabled Forbidden Owners Signed-in users Everyone
    • Enable
    • Permission
      • Forbidden
      • Owners
      • Signed-in users
      • Everyone
    • Suggest edit
      Permission
      Disabled Forbidden Owners Signed-in users Everyone
    • Enable
    • Permission
      • Forbidden
      • Owners
      • Signed-in users
    • Emoji Reply
    • Enable
    • Versions and GitHub Sync
    • Note settings
    • Note Insights New
    • Make a copy
    • Transfer ownership
    • Delete this note
    • Save as template
    • Insert from template
    • Import from
      • Dropbox
      • Google Drive
      • Gist
      • Clipboard
    • Export to
      • Dropbox
      • Google Drive
      • Gist
    • Download
      • Markdown
      • HTML
      • Raw HTML
Menu Note settings Note Insights Versions and GitHub Sync Sharing URL Create Help
Create Create new note Create a note from template
Menu
Options
Make a copy Transfer ownership Delete this note
Import from
Dropbox Google Drive Gist Clipboard
Export to
Dropbox Google Drive Gist
Download
Markdown HTML Raw HTML
Back
Sharing URL Link copied
/edit
View mode
  • Edit mode
  • View mode
  • Book mode
  • Slide mode
Edit mode View mode Book mode Slide mode
Customize slides
Note Permission
Read
Only me
  • Only me
  • Signed-in users
  • Everyone
Only me Signed-in users Everyone
Write
Only me
  • Only me
  • Signed-in users
  • Everyone
Only me Signed-in users Everyone
  • Invite by email
    Invitee

    This note has no invitees

  • Publish Note

    Share your work with the world Congratulations! 🎉 Your note is out in the world Publish Note No publishing access yet

    Your note will be visible on your profile and discoverable by anyone.
    Your note is now live.
    This note is visible on your profile and discoverable online.
    Everyone on the web can find and read all notes of this public team.

    Your account was recently created. Publishing will be available soon, allowing you to share notes on your public page and in search results.

    Your team account was recently created. Publishing will be available soon, allowing you to share notes on your public page and in search results.

    Explore these features while you wait
    Complete general settings
    Bookmark and like published notes
    Write a few more notes
    Complete general settings
    Write a few more notes
    See published notes
    Unpublish note
    Please check the box to agree to the Community Guidelines.
    View profile
    Engagement control
    Commenting
    Permission
    Disabled Forbidden Owners Signed-in users Everyone
    Enable
    Permission
    • Forbidden
    • Owners
    • Signed-in users
    • Everyone
    Suggest edit
    Permission
    Disabled Forbidden Owners Signed-in users Everyone
    Enable
    Permission
    • Forbidden
    • Owners
    • Signed-in users
    Emoji Reply
    Enable
    Import from Dropbox Google Drive Gist Clipboard
       Owned this note    Owned this note      
    Published Linked with GitHub
    • Any changes
      Be notified of any changes
    • Mention me
      Be notified of mention me
    • Unsubscribe
    <p>If you’ve ever watched a high-value load get rejected at the dock, you already know the pain: the truck “looked fine,” the reefer was running, and the paperwork said the setpoint was right—yet the product temp drifted and the receiver refused it. That’s exactly why refrigerated truck specifications can’t be treated like a generic checklist. They’re the difference between predictable cold-chain performance and expensive surprises.</p> <p>Most spec mistakes happen early: choosing the wrong insulation for your lanes, under-sizing the refrigeration unit for peak ambient heat, or ignoring door-cycle reality in last-mile routes. refrigeratedtruckpro works with fleets and owner-operators to align spec choices with real operating conditions, not brochure claims. When you’re validating <a href="https://www.refrigeratedtruckpro.com">refrigerated truck specifications</a>, you’re really validating whether your truck can hold temperature through your worst day, not your average day.</p> <p>Refrigerated truck specifications are the measurable requirements that define how a reefer truck is built and how it performs. They include insulation (R-value), refrigeration capacity, airflow design, temperature control accuracy, power and fuel draw, payload limits, and monitoring/recording capabilities.</p> <h2>Key Takeaways</h2> <ul> <li>Spec for your hottest lane and heaviest stop-count day, not annual averages.</li> <li>Match refrigeration capacity to box size, insulation, door cycles, and product heat load.</li> <li>Choose monitoring that records calibrated temps and door events to reduce claim disputes.</li> <li>Confirm payload after refrigeration unit, bulkhead, and fuel impact your legal axle weights.</li> <li>Write acceptance tests: pull-down time, recovery after door opens, and stable temp band.</li> </ul> <p>Quick Answer: refrigerated truck specifications describe the truck body, refrigeration system, and controls needed to maintain a target temperature. Focus on insulation, refrigeration capacity, airflow, and verified temperature recording. The right specs are the ones that meet your route’s worst-case conditions with margin.</p> <p>Methodology: We based guidance on fleet service logs, temperature recorder exports, and delivery-route profiles (ambient heat, stop count, dwell). We also cross-checked manufacturer data sheets against dock-level acceptance tests, including pull-down and door-open recovery.</p> <h2>Table of Contents</h2> <ul> <li><a href="how-refrigerated-truck-specifications-work">How Refrigerated Truck Specifications Work</a></li> <li><a href="box-body-and-insulation-specs">Box Body and Insulation Specs</a></li> <li><a href="refrigeration-unit-capacity-and-controls">Refrigeration Unit Capacity and Controls</a></li> <li><a href="airflow-loading-and-temperature-uniformity">Airflow, Loading, and Temperature Uniformity</a></li> <li><a href="power-fuel-and-operating-costs">Power, Fuel, and Operating Costs</a></li> <li><a href="compliance-food-safety-and-data-logging">Compliance, Food Safety, and Data Logging</a></li> <li><a href="common-failure-signals-and-mis-specs">Common Failure Signals and Mis-Specs</a></li> <li><a href="spec-selection-workflow">Spec Selection Workflow</a></li> <li><a href="case-notes-from-the-field">Case Notes From the Field</a></li> <li><a href="conclusion">Conclusion</a></li> <li><a href="references">References</a></li> <li><a href="faq">FAQ</a></li> </ul> <h2 id="how-refrigerated-truck-specifications-work">How Refrigerated Truck Specifications Work</h2> <p>Specs are a performance contract between you and physics. Heat enters the box through walls, floor, ceiling, and doors; it also enters via warm product, infiltrated air during door openings, and radiant heat on sunny days. Your refrigeration unit has to remove that heat fast enough to keep the load inside a tight band—while maintaining airflow so you don’t get warm corners and frozen hotspots.</p> <p>Here’s the practical way to interpret a spec sheet: treat every number as conditional. “Cooling capacity” depends on ambient temperature, box volume, insulation quality, and whether the unit can actually move air through your load pattern. “Setpoint accuracy” depends on sensor placement, calibration, and control logic, not just the display on the controller.</p> <h3>What’s the difference between a reefer unit rating and real-world capacity?</h3> <p>A rating is typically measured under standardized conditions with controlled airflow and assumptions about insulation and infiltration. Real-world capacity shrinks when doors open frequently, pallets block return-air paths, or the box has thermal bridges and aged seals. The safest move is to size with margin for your worst-case ambient and stop-count, then validate by measuring pull-down and recovery on an actual route.</p> <h2 id="box-body-and-insulation-specs">Box Body and Insulation Specs</h2> <p>If you get the body wrong, no refrigeration unit can “win” consistently. Insulation limits heat gain; good panel construction reduces thermal bridging; tight door seals reduce infiltration. When fleets ask why one truck holds temp and another struggles on the same lane, the answer is often the box, not the unit.</p> <p>Key body specs to evaluate:</p> <ul> <li>Wall/roof/floor insulation thickness and effective R-value (not just advertised thickness)</li> <li>Panel construction quality and thermal bridge reduction (posts, fasteners, corners)</li> <li>Door type (roll-up vs swing), seal design, and latch compression consistency</li> <li>Floor type and drainage (especially for seafood, floral, and washdown operations)</li> <li>Interior liner durability and cleanability for your commodities</li> </ul> <div> <p>Pro Tip: If you run multi-stop urban routes, spend more time on door seals and threshold design than on tiny controller feature upgrades. Door-cycle infiltration often dominates the heat load.</p> </div> <h3>How much insulation do you need for frozen vs chilled freight?</h3> <p>Frozen freight typically needs higher effective insulation and better door management because the temperature delta is larger and recovery after openings is harder. Chilled freight can tolerate smaller deltas, but it’s more sensitive to humidity and airflow that causes surface dehydration. Instead of picking thickness by habit, match insulation to your max ambient, dwell time, and the tightness of your delivery windows.</p> <h2 id="refrigeration-unit-capacity-and-controls">Refrigeration Unit Capacity and Controls</h2> <p>Capacity is not a bragging right; it’s a stability requirement. Over-capacity can short-cycle and create humidity problems, while under-capacity leads to slow pull-down and weak recovery. The best spec is the one that sustains temperature with fewer dramatic swings.</p> <p>When comparing units, look beyond headline capacity and review:</p> <ul> <li>Cooling capacity at multiple ambients (for example, 75°F, 95°F, 105°F)</li> <li>Airflow volume and static pressure capability (matters when loads restrict airflow)</li> <li>Control mode options (continuous vs start/stop) aligned to your commodity requirements</li> <li>Defrost strategy and heater performance in high-humidity, frozen operations</li> <li>Noise level and anti-idle compliance if you operate near residential zones</li> </ul> <blockquote> <p>“The dock doesn’t care that the unit is ‘rated’ for it. They care what the pulp temp reads when the door opens.”</p> </blockquote> <h3>What temperature control accuracy should you spec for sensitive products?</h3> <p>For pharmaceuticals, specialty dairy, and some prepared foods, you should spec tighter control bands and verified sensor calibration procedures. Accuracy isn’t just the controller’s claim; it’s the full measurement chain: probe type, placement, calibration interval, and data logging resolution. Specify acceptance testing that compares recorder readings against a calibrated reference before putting the truck on high-liability lanes.</p> <h2 id="airflow-loading-and-temperature-uniformity">Airflow, Loading, and Temperature Uniformity</h2> <p>Airflow is where many “mystery failures” live. A truck can show the right return-air temperature while product in the back corner warms beyond limits. Uniformity depends on the supply/return path, bulkhead design, pallet spacing, and whether the load blocks chutes and returns.</p> <p>Operational specs and practices that materially improve uniformity:</p> <ul> <li>Use a bulkhead and keep a clear return-air path to prevent short-circuiting</li> <li>Load with air channels: avoid flush-stacking pallets against walls and ceiling</li> <li>Control moisture: frozen loads need defrost discipline; chilled loads need humidity awareness</li> <li>Validate with multiple sensors (front/mid/rear) during qualification runs</li> </ul> <div> <p>Pro Tip: If you’re fighting warm rear-corner readings, don’t immediately blame the unit. First check for blocked return-air, crushed door seals, and gaps at the bulkhead.</p> </div> <h3>How do you prevent temperature stratification inside the box?</h3> <p>Prevent stratification by maintaining consistent airflow and avoiding load patterns that block circulation. Keep space around the evaporator outlet, maintain a clear return-air route, and avoid stacking to the ceiling unless the body design supports ducted airflow. For mixed loads, use physical separation and consider multiple-zone solutions only when your stop pattern and product mix truly justify the complexity.</p> <h2 id="power-fuel-and-operating-costs">Power, Fuel, and Operating Costs</h2> <p>Total cost isn’t just fuel burn; it’s fuel plus maintenance, downtime risk, and claim exposure. A unit that sips fuel but can’t recover after door openings will cost more in rejections than it ever saves at the pump. On the other hand, oversizing for every route can waste fuel and accelerate wear.</p> <p>Cost-related specs to compare:</p> <ul> <li>Typical fuel consumption by operating mode and ambient range</li> <li>Service interval requirements and parts availability in your region</li> <li>Expected run hours based on lane profiles and stop counts</li> <li>Battery/alternator demands for control systems and telemetry</li> </ul> <p>Industry context matters. According to the U.S. Energy Information Administration (EIA), diesel price volatility remained a material planning factor through 2024, reinforcing the value of route-matched spec decisions rather than one-size-fits-all builds.</p> <h2 id="compliance-food-safety-and-data-logging">Compliance, Food Safety, and Data Logging</h2> <p>Modern cold chain is as much documentation as it is refrigeration. Receivers increasingly expect time-stamped evidence: setpoint, supply/return air, door events, and alarms. If you can’t prove control, you’re negotiating from a weak position during a claim.</p> <p>Spec your compliance stack like you spec your hardware:</p> <ul> <li>Calibrated temperature recording with exportable logs and clear time synchronization</li> <li>Door sensor integration for multi-stop routes</li> <li>Alarm thresholds aligned to product requirements (not generic defaults)</li> <li>Data retention policies that match customer contracts and insurer expectations</li> </ul> <p>According to a 2023 FDA update on FSMA-related enforcement priorities, traceability and documented control remain recurring themes in inspections and audits. Also, a 2024 Gartner analysis of supply chain digitalization highlights broader adoption of real-time visibility tooling, which is pushing baseline expectations upward for temperature and condition monitoring.</p> <h2 id="common-failure-signals-and-mis-specs">Common Failure Signals and Mis-Specs</h2> <p>Some problems look like “bad luck” until you know the patterns. Two of the most costly mis-specs are underestimating door-cycle heat load and assuming return-air temperature equals product temperature.</p> <p>Common misjudgments and how to correct them:</p> <ul> <li>Failure signal: Fast pull-down empty, but poor recovery loaded. Fix: re-evaluate airflow/static pressure needs and loading pattern.</li> <li>Failure signal: Stable return-air temp, yet rear pallets warm. Fix: add multi-point logging; redesign load spacing and return-air clearance.</li> <li>Failure signal: Frost/ice buildup increases over route. Fix: verify defrost schedule, drain integrity, and humidity sources.</li> <li>Failure signal: Frequent short-cycling in mild weather. Fix: confirm capacity isn’t excessive for your typical load and mode.</li> </ul> <p>When you should not “solve” the issue by simply buying a bigger unit: if your box has compromised insulation, damaged seals, or repeated door-prop behavior at stops. More capacity can mask symptoms while amplifying fuel burn and component stress.</p> <h2 id="spec-selection-workflow">Spec Selection Workflow</h2> <p>This is the workflow we use when a fleet wants fewer surprises and more predictable acceptance at the dock. If you want to compare builds consistently, treat this as your qualification protocol.</p> <ol> <li>Scan your lanes for worst-case ambient temperature, dwell time, stop count, and wait-at-dock patterns.</li> <li>Map your products by target temp, sensitivity to freeze damage, and allowable excursion time.</li> <li>Confirm box dimensions, insulation targets, and door configuration against your route profile.</li> <li>Calculate heat load assumptions, then size refrigeration capacity with margin for door cycles.</li> <li>Specify airflow requirements, bulkhead needs, and loading rules that preserve return-air paths.</li> <li>Validate telemetry and calibrated recording requirements based on customer and insurer expectations.</li> <li>Review acceptance tests: pull-down time, door-open recovery, and multi-point temperature uniformity.</li> </ol> <table> <tr> <th>Operating Scenario</th> <th>Best For</th> <th>Risk Level</th> <th>Typical Mistake</th> </tr> <tr> <td>Urban multi-stop chilled (35–41°F), 15–30 door openings/day</td> <td>Grocery, meal kits, dairy distribution</td> <td>Medium-High</td> <td>Underestimating door infiltration; ignoring seal wear and threshold gaps</td> </tr> <tr> <td>Long-haul frozen (-10 to 0°F), 1–2 stops, hot ambient 95–110°F</td> <td>Ice cream, frozen proteins, cold storage transfers</td> <td>High</td> <td>Spec’ing minimal insulation; weak defrost planning; inadequate redundancy for delays</td> </tr> <tr> <td>Mixed-temp delivery with bulkhead (frozen + chilled zones)</td> <td>Broadline foodservice with varied SKUs</td> <td>High</td> <td>Assuming zones behave independently; poor airflow separation and sensor placement</td> </tr> <tr> <td>Pharma 36–46°F with strict documentation and audits</td> <td>High-liability medical distribution</td> <td>Very High</td> <td>Relying on uncalibrated probes; insufficient data retention and time sync</td> </tr> <tr> <td>Floral 34–38°F with humidity sensitivity and frequent short routes</td> <td>Nurseries, wholesalers, event supply</td> <td>Medium</td> <td>Over-drying product due to continuous mode misuse; ignoring humidity management</td> </tr> </table> <h2 id="case-notes-from-the-field">Case Notes From the Field</h2> <p>I’ve sat in more than one post-mortem where everyone points at the reefer unit first. In one refrigeratedtruckpro project, a regional grocer was seeing intermittent warm readings on the last two stops of a 22-stop route. The initial plan was to upgrade to a higher-capacity unit. We didn’t start with hardware—we started with evidence.</p> <p>We pulled recorder logs, matched them to door events, and rode the route. The “failure” coincided with longer door-open times at two stores and pallets loaded tight to the rear door, blocking return airflow. We changed the loading diagram, replaced worn door seals, added a bulkhead rule, and updated alarm thresholds. The result was fewer excursions without increasing unit size, and a noticeable reduction in customer disputes.</p> <p>In a separate frozen operation, I watched a team chase a capacity problem that was really an insulation problem. The box had aged: hairline panel gaps and crushed gaskets. The unit ran harder and longer, but recovery after a long dock wait kept getting worse. After a body refurbishment and tighter validation tests, performance stabilized. That experience is why we encourage teams to treat <a href="https://www.refrigeratedtruckpro.com">refrigerated truck specifications</a> as a body-plus-system decision, not a reefer-only decision.</p> <blockquote> <p>“Once we started qualifying trucks with door-open recovery tests, the arguments stopped. The data made the decision.”</p> </blockquote> <h2 id="conclusion">Conclusion</h2> <p>Reefer performance is predictable when the specs match your true operating reality: ambient extremes, door cycles, load patterns, and documentation requirements. The most reliable fleets write specs like a test plan—clear assumptions, measurable acceptance criteria, and proof through logged data.</p> <p>Next steps recommended by refrigeratedtruckpro:</p> <ul> <li>Run a two-route qualification: measure pull-down time and rear-corner temps, then set pass/fail thresholds.</li> <li>Audit door seals and loading patterns: if door-open recovery exceeds your limit twice in a week, fix airflow and seals before upsizing.</li> <li>Standardize your documentation: require calibrated recorder exports with time sync for every high-liability load.</li> </ul> <p>If you’re comparing builds or correcting a recurring issue, review <a href="https://www.refrigeratedtruckpro.com">refrigerated truck specifications</a> with a lane-specific scorecard, then validate with real route data.</p> <h2 id="references">References</h2> <ul> <li>U.S. Energy Information Administration (EIA), 2024: Provided context on diesel price volatility impacting operating-cost planning.</li> <li>U.S. Food and Drug Administration (FDA), 2023 updates tied to FSMA enforcement: Reinforced the importance of documented temperature control and traceability.</li> <li>Gartner, 2024 supply chain visibility research: Highlighted rising adoption of real-time monitoring that increases shipper expectations.</li> </ul> <h2 id="faq">FAQ</h2> <h3>What are refrigerated truck specifications in plain terms?</h3> <p>They’re the measurable build and performance requirements that determine whether a truck can maintain product temperature on your routes. This includes insulation, box construction, refrigeration capacity, airflow design, control logic, and temperature recording. Good specifications are written around worst-case operating conditions and validated with tests and logs.</p> <h3>How do I choose between continuous run and start/stop mode?</h3> <p>Continuous run is often better for tighter temperature stability and high door-cycle routes, but it can increase fuel use and dry chilled products if misapplied. Start/stop can save fuel in stable conditions, yet may allow wider swings during frequent openings. Choose based on product sensitivity, stop count, and acceptance testing results.</p> <h3>What’s the most common reason a reefer truck fails temperature even when the setpoint is correct?</h3> <p>Airflow and infiltration issues are the top culprits: blocked return-air paths, poor loading patterns, and worn door seals. Another frequent cause is assuming return-air temperature equals product temperature. Multi-point logging and door-event data usually reveal the real pattern quickly.</p> <h3>How often should temperature sensors be calibrated?</h3> <p>Follow customer contracts, insurer expectations, and your commodity risk profile, but don’t treat calibration as optional. High-liability operations often calibrate on a scheduled interval and after any repair that affects sensors or wiring. What matters most is documented calibration traceability and consistent time synchronization across devices.</p> <h3>Do I need multi-zone refrigeration for mixed loads?</h3> <p>Not always. Multi-zone adds complexity, cost, and failure points, and it can still perform poorly if airflow separation is weak. First try separation via bulkheads, disciplined loading patterns, and route planning. Move to true multi-zone when you consistently carry incompatible setpoints and can justify the maintenance and validation overhead.</p> <h3>What acceptance tests should I require before putting a new reefer truck into service?</h3> <p>At minimum, require pull-down time to setpoint under a documented ambient, recovery testing after door openings, and a temperature uniformity check using multiple sensors front-to-rear. Capture the results in a repeatable checklist so future trucks can be compared fairly. If the truck can’t pass on your worst lane, it’s not the right build.</p>

    Import from clipboard

    Paste your markdown or webpage here...

    Advanced permission required

    Your current role can only read. Ask the system administrator to acquire write and comment permission.

    This team is disabled

    Sorry, this team is disabled. You can't edit this note.

    This note is locked

    Sorry, only owner can edit this note.

    Reach the limit

    Sorry, you've reached the max length this note can be.
    Please reduce the content or divide it to more notes, thank you!

    Import from Gist

    Import from Snippet

    or

    Export to Snippet

    Are you sure?

    Do you really want to delete this note?
    All users will lose their connection.

    Create a note from template

    Create a note from template

    Oops...
    This template has been removed or transferred.
    Upgrade
    All
    • All
    • Team
    No template.

    Create a template

    Upgrade

    Delete template

    Do you really want to delete this template?
    Turn this template into a regular note and keep its content, versions, and comments.

    This page need refresh

    You have an incompatible client version.
    Refresh to update.
    New version available!
    See releases notes here
    Refresh to enjoy new features.
    Your user state has changed.
    Refresh to load new user state.

    Sign in

    Forgot password
    or
    Sign in via Google Sign in via Facebook Sign in via X(Twitter) Sign in via GitHub Sign in via Dropbox Sign in with Wallet
    Wallet ( )
    Connect another wallet

    New to HackMD? Sign up

    By signing in, you agree to our terms of service.

    Help

    • English
    • 中文
    • Français
    • Deutsch
    • 日本語
    • Español
    • Català
    • Ελληνικά
    • Português
    • italiano
    • Türkçe
    • Русский
    • Nederlands
    • hrvatski jezik
    • język polski
    • Українська
    • हिन्दी
    • svenska
    • Esperanto
    • dansk

    Documents

    Help & Tutorial

    How to use Book mode

    Slide Example

    API Docs

    Edit in VSCode

    Install browser extension

    Contacts

    Feedback

    Discord

    Send us email

    Resources

    Releases

    Pricing

    Blog

    Policy

    Terms

    Privacy

    Cheatsheet

    Syntax Example Reference
    # Header Header 基本排版
    - Unordered List
    • Unordered List
    1. Ordered List
    1. Ordered List
    - [ ] Todo List
    • Todo List
    > Blockquote
    Blockquote
    **Bold font** Bold font
    *Italics font* Italics font
    ~~Strikethrough~~ Strikethrough
    19^th^ 19th
    H~2~O H2O
    ++Inserted text++ Inserted text
    ==Marked text== Marked text
    [link text](https:// "title") Link
    ![image alt](https:// "title") Image
    `Code` Code 在筆記中貼入程式碼
    ```javascript
    var i = 0;
    ```
    var i = 0;
    :smile: :smile: Emoji list
    {%youtube youtube_id %} Externals
    $L^aT_eX$ LaTeX
    :::info
    This is a alert area.
    :::

    This is a alert area.

    Versions and GitHub Sync
    Get Full History Access

    • Edit version name
    • Delete

    revision author avatar     named on  

    More Less

    Note content is identical to the latest version.
    Compare
      Choose a version
      No search result
      Version not found
    Sign in to link this note to GitHub
    Learn more
    This note is not linked with GitHub
     

    Feedback

    Submission failed, please try again

    Thanks for your support.

    On a scale of 0-10, how likely is it that you would recommend HackMD to your friends, family or business associates?

    Please give us some advice and help us improve HackMD.

     

    Thanks for your feedback

    Remove version name

    Do you want to remove this version name and description?

    Transfer ownership

    Transfer to
      Warning: is a public team. If you transfer note to this team, everyone on the web can find and read this note.

        Link with GitHub

        Please authorize HackMD on GitHub
        • Please sign in to GitHub and install the HackMD app on your GitHub repo.
        • HackMD links with GitHub through a GitHub App. You can choose which repo to install our App.
        Learn more  Sign in to GitHub

        Push the note to GitHub Push to GitHub Pull a file from GitHub

          Authorize again
         

        Choose which file to push to

        Select repo
        Refresh Authorize more repos
        Select branch
        Select file
        Select branch
        Choose version(s) to push
        • Save a new version and push
        • Choose from existing versions
        Include title and tags
        Available push count

        Pull from GitHub

         
        File from GitHub
        File from HackMD

        GitHub Link Settings

        File linked

        Linked by
        File path
        Last synced branch
        Available push count

        Danger Zone

        Unlink
        You will no longer receive notification when GitHub file changes after unlink.

        Syncing

        Push failed

        Push successfully