Southern California's AllFlat provides best-of-breed hardware and software solutions to flatten your world.
What's New: Mail Menu, Isopleth Standard, TR34 Free Movement, Why Ninety Five Percent, and App Versions.
And this FLIP version got etched Even and Odd symbols on their feet!
🎉🌟💫✨❧✨💫🌟🎉🌟💫✨❧✨💫🌟🎉🌟💫✨❧✨💫🌟🎉
Our surveying and grinding system sends floor smoothness signals to AllFlat tablets that constrain floors to safety tolerance standards such as CS TR34 EN 15620:2008 ASTM E1155 and DIN 18202
The goal is to draw a straight line on a floor, call it a "Track," measure its smoothness Readings at regular Steps, store the Steps in a Run record, cleanse & assemble their numbers, compare them to industry standards, determine where to grind, show grinding progress, and publish reports — informes — describing progress flattening and leveling the Track.
This app finds, fixes, and confirms floor improvements in smoothness, categorized by flatness and levelness. Flatness is each point's absolute altitude from a nearby origin and Levelness is a relative slope line or dip plane thru a tangent of sample points for at a given point. We make those F and L numbers common and comparable with other floors, equipment, contractors, and sometimes alternate survey techniques. We forgot their original unit (often a weighted reciprocal of a square root of a slope) to give them a new comparable unit following common industry sample rates and calibrations.
All Tracks belong to a Section, representing specific slabs or pours of concrete, and all Sections belong to a Surface, which is a category of Sections such as one building or one floor construction technique. All areas belong to a Project, which is the complete set of Runs sharing the same statistical Standards, Surfaces in one Site, and time frame. As a practical matter for all layers, all Projects should be small and publishable.
Each Run has a name, such as SN3 b, where SN3 is the Track name, and b identifies
the Run. The various standards' math should analyze only one Run per Track per Project;
Use the Aggregate Check Box or Include Run Check Box to exclude all incomplete or
overlapping Run attempts.
💡 This symbol represents a Good Idea to try, such as "all names are case
insensitive"; 1SN matches 1sN (and it means Track 1 from South to North).
💣 This symbol represents a Bad Idea to not try, such as "no exploiting case insensitivity." App Planar Infinity can fix case mismatches.
🌱 Reports display at any resolution and orientation; try it. This is a Lean and Green suggestion.
🌱 Keep all Lithium Ion batteries topped off, preventing full charge by remembering the previous. Full batteries draw zero charge; the tiny trickle just keeps the zillion wire gates fresh but idle at extremely low current.
These things lead the system:
Planar Infinity also sports a bicameral controller model; a small controller inside the Device paired over Bluetooth to a dedicated high-end tablet viewing and controlling it.
Planar Infinity también cuenta con un modelo de controlador bicameral; un pequeño controlador dentro del Dispositivo emparejado (paired) por Bluetooth con una tableta dedicada de alta gama que lo visualiza y controla.
This is the goal: A region flattened just enough that it achieves tolerance within the lines.
The red line is before and the black line is after grinding at the indicated points:
The phases of activity are:
As fases das atividades son:
Durante la encuesta, se recolecta ( Collect Run Button ) un proyecto completo de ejecuciones entre los intentos de rectificación. El análisis transforma los datos de elevación en resultados estadísticos (mira Edit Run Report ), incluidas comparaciones ( Comparisons ) con estándares ( Project Form ) de la industria. Estas identifican áreas que requieren rectificación. La exclusión de ejecuciones incompletas o superpuestas incluye funcionalidades para desestimar intentos de ejecución incompletos o superpuestos del análisis, asegurando precisión. Se planifica y se corrigen ( Grind Tickets ) los suelos. Se inicia un nuevo proyecto y se mide el progreso. Se comparan con el proyecto anterior en el mismo sitio y horizonte. Se evalúa el progreso hacia buenos índices de planitud. Y repeat.
A Run Report describes one track's elevation profile sampling event in every possible detail, including all input configurations, and the rough point in space and time. Various labels and outputs will come and go between various hardware types:
That tested a Profileograph on a long, deliberately bad floor. The low blue Transverse profile means the right side of the aisle needs grinding because a forklift would operate with its mast too far to its left, or starboard.
In summary:
The system transforms unsafe floor surfaces into tight, reliable pathways through meticulous data collection, analysis, and improvement efforts via statistics and facts on the ground using measurements, statistics, and comparisons.
The Profiles show where to grind. The Red :🇸🇬: Longitudinal profile in the middle of an aisle and the Blue :🇸🇻: Transverse profiles on either side of the middle. When you grind, account for the length of the Arms. The profiles must fit within tolerance bands as permitted elevations.
This is an ASTM E1155 Free Movement Run Report in your mobile device, showing a Run on the second South to North Track in Section "Pour3":
In the reports, N/A means either "Not Available," "Not Applicable," or "overcome by events."
By the same reckoning, -- in the reports means "nothing to see here; not specified; not even
labeled. No real number appears in this location but we must pad the report out." Put another way,
an N/A always has a failed label somewhere however a -- isn't a variable so it's nameless.
En los informes, N/A significa "No Disponible," "No Aplicable," o
"superado por los acontecimientos." Los dos guiones -- significan "no es asunto tuyo;
nada aqui."
🌱 The reports appear in two places — the tablet app's report panel, and as HTML pages.
The Edit Run Report contains a few controls to clean and tweak the data. The Globe Button raises only the reports, in the default web browser, for rapid viewing while analyzing a Project.
💡 Open the 📃 Internal Run Report and tap the 🔒 lock button to run the Edit Run Report, and toggle whether the current Run is editable.
🌱 This is the end of the introduction; the tech is next.
From here you should go back to the Table of Contents or Domain Objects, or forward to the Logo Menu, Tool Bar, Status Bar, or into ASTM E1155, DIN 18202, any TR34, EN 15620, Profile Chart, Keypad Row, Edit Run Report, Tool Bar, or the Globe Button.
The English language versions of international standards require our reports and thereby our view to match their International English for secure reference, therefor the tablet cannot internationalize its view. While any translation tool will easily get the gist and numbers right, always keep a report's English original with it because the rules of surveying are that different kinds of data in different surveys to the same Property must all match each other reliably, so translations can't match up the Properties by name. In English, the crew and tools see at a glance which floor won a Property contest.
For the home user experience, any virtual keyboard installed on a tablet will enter the user's text for languages from any continent, effectively contrasting with stale overused English terms, enhancing report clarity:
"Bidi" means bi-directional text; the Arabic flows from right to left, saying "interesting" as مثير للاهتمام.
This ruggedized Android tablet runs App Planar Infinity to drive AllFlat's floor analysis tools and process their output.
Always tune everything to these settings:
allflat.fmp0004gmail.com, to mail reports out
Because air-gapping a battery preserves it, AllFlat hardware plug in the battery to activate its device.
🌱 Batteries are a single point of failure and they are a cheap consumer commodity, so AllFlat devices mount their USB-C battery outside the chassis. The Surveyor should keep two in the kit and use the one that works best.
🌱 Always fully charge the spare before downtime; never disappoint anyone picking up a cold battery.
💣 USB batteries cannot transmit their power levels on their wire, so your tablet cannot prevent you from starting a Run with the battery too low. So in exchange for the convenience of USB batteries always check the level manually.
✈️ Remember the big batteries go in your carry-on, not in your checked luggage.
Our floor flatness measuring devices detect surface elevation readings and collect them into a microcontroller which sends Bluetooth signals to an Android tablet running App Planar Infinity for processing.
To get started, connect power to the device and wait a minute. On the Android tablet, use the Settings application to make sure Bluetooth is turned on, then search the Bluetooth spectrum for a host named by some variation of "FLIPSN00099." Tap the Pair button, and confirm the tablet and Level Signal Controller have exchanged their pairing identifiers.
💡 The name of the Level Signal Controller is the name of the Device, and it appears in all outputs. The Device's microcontroller's $HOST name and Bluetooth channel must equal the Device Name in the system at all times.
💣 There is no truth to the rumor that AllFlat personnel refer to the Level Signal Controller as "the Minion." No hay verdad en el rumor de que el personal de AllFlat se refiera al Controlador de Señal de Nivel como "el Minion".
This application runs on an Android Tablet, and AllFlat upgrades its versions early and often. Use the Logo Menu's Upgrade App item to check for a new App Version at any time.
The app supports two tablet roles:
🌱 In a pinch a Device tablet may analyze other Device tablets; this practice is not naturally scalable; tablets are cheap.
Your App Planar Infinity accumulates versions as *.apk files in your Downloads folder,
letting you choose which feature set to run. You may change the version at any
time between major releases because the database schema is frozen and all new fields are
sparse, transparent, and preserved.
🌱 Recycle the older files lest they mislead you.
Speak with AllFlat personnel, down to our crack CNC lathe operating team DF or JC, about which version is right for you, your gear, & your project!
The files are named planarInfinityMarchFLIP.apk,
planarInfinityOctoberContour.apk, planarInfinitySeptember.apk, etc. The Logo Menu has
an Upgrade App item that tells you what version you have and how to upgrade.
A version suffix, such as JanuaryFLIP_Q contains two sub-fields; the date and
an incentive to install the patch; what system got improved.
🌱 If your system is collecting well, get AllFlat permission before leveling up; do not install a new version recreationally. Some may disrupt your procedures, such as renaming CSV to TSV files. If you don't already have a reason, check AllFlat chatter to learn of new features. Some few fixes such as for a broken file record format are mandatory for everyone. All fixes are aware of all hardware and standards and generally do not interfere with the legacy systems that work.
And Version EE got etched Even and Odd sigils on the FLIP feet, too!
Here's the version with global TSV downloads.
Coming versions will feature:
Note that apps leveling up to SDK 36 won't work in the field with older.
Each of these tablets bond with one robot to drive it, record its data, and publishes individual accounts of it using the Mail Menu.
It optionally mails its Project Report data to an:
These tablets have only an Import button in the lower right corner on Keypad Row. It invokes the Import Project Report Wizard, whose first page is the system filepicker.
They use the Mail Menu to broadcast Project Reports that represent the flatness and levelness of the same zone over different devices; both Profileographs and FLIPs.
🌱 In a pinch a Device tablet may analyze other Device tablets; all the core features are the same just the tablet Standard Operating Procedures should be different.
The life of an Analyst Tablet...
...is to subject multiple Runs from various sources to common force multipliers in the regulatory Standards. It alone can produce reports — From Device Tablets Project Reports, thus creating Project Index, Project Report, and Combined Test Sections Report — which vouch for the flatness and levelness of a given region according to a team of robots.
Follow this procedure:
The Standards' statistics will now include all the imported Runs, ensuring that the final reports reflect the full scope of the data collected in the field.
Remember that an Analyst tablet now breaks every social more (pronounced moray) against data from Profileograph devices rubbing elbows with data from FLIP devices. App Planar Infinity abides. The Standards will not mix Runs that use other Standards.
💡 As a convenience, the Analyst Tablet may now perform minor edits on imported Runs. However, 💣 re-importing the Runs will naturally overwrite these edits. Surveyors should make any required edits to the Surveying Runs before exporting them to ensure that all changes are preserved.
Also, a Device Tablet should not send Runs to another Device Tablet, which then forwards them to the Analyst Tablet. The Analyst Tablet should only assimilate fresh Runs from their original tablets to maintain data integrity and avoid potential conflicts.
On the Android tablet, tap its application icon to invoke Planar Infinity:
When collecting a Run, the screen resembles this early rough sketch:
These this shows the Keypad Row in its data collection mode:
The elements include the Status Bar, Tool Bar, Profile Chart, Grind Tickets, and Keypad Row in the lower right.
App Planar Infinity displays its current situation in the stripe atop its screen. An Analyst Tablet sees the Run's title in green.
While watching a Device Tablet's status bar, lift an arm to see its signal change. That verifies which arm uses which sensor. When the Device is configured, the status bar displays calculated elevations. If the Device is not configured, the status bar shows the sensors' raw signals (containing the sensors' serial numbers), and when new Readings come in, they display here. Your device may have fewer or more sensor arms than this.
New Readings during device maintenance and Steps display here.
If the numbers are too small, tap the Status Bar to enlarge them. Tap them again to shrink them.
Below the Status Bar, the white stripe of tools atop the Profile Chart provide popups to process the Domain Objects and configure, find, analyze, and broadcast Runs. (Use the mighty Keypad Row in the lower right to collect Runs or Import Runs.)
ᚼᛒ Bluetooth signal level gaugeCurrent Run Time — tap this for the Run Index This provides a few global App Planar Infinity configurations, and access to
the Engine Form for FLIP Manufacturing,
which should only be used when manufacturing a new Device.
💣 If your tablet has no Wi-Fi connection, the menu says "No Wi-Fi."
Tip: You can copy this file out of the browser and take it with you, self-contained. That means you can read the help file on another device while operating the tablet, without this screen in your way! Use your browser's download page feature.
This miniature web server displays every report, including inside the tablet and sometimes outside. All pages are anonymous and read-only, and the server dislikes being left on. The website serves to preview reports, in large desktop monitors, before package those reports into a mail with the Mail Menu.
🌱 To save electricity, this website is off when a tablet's screen is off.
As an information radiator, App Planar Infinity tablets serve web page reports. If the connected Wi-Fi router agrees, the Logo Menu displays your tablet's network IP number inside a web address for you to copy into your device on the same net. The check box gates access to the system.
Type the address exactly as shown. While the box is checked, any web browser on the same network
may hit this address. Type in all the extra parts of the address, including the protocol http://
with a root path and ending always w/ port :8000. The extra typing forces an anonymous,
read-only, portable website.
💣 It's not https:// — take out the S. Your browser will try to add it AND will hide
it from you!
💣 Do not type it into a search field; use the address bar at the very top of the browser window.
The small website emits the Run Index, each Run Report, each Project Report, and any statistical reports. The reports contain the same output data as the Mail reports.
The website is the best way to read huge reports that munch thru the same numbers in different ways. See the Globe Button to browse the Project Report inside the tablet.
All website pages generally match the mails, and the Import Project Wizard can read them. See the Mail Menu. Read the Globe Button for tips on sharing a link to the website.
💡 If your mail agent or server refuse to transmit (we followed the rules!), turn on the website and scrape its web pages to get your content. Just don't bulk copy-and-paste it into a word processor! That scrambles the formatting, assuming you like to spend hours cleaning up. Use a Context Menu, such as the second mouse button, on the links to download them.
🌱 To send a link to your desktop, activate the External Website, tap your friendly neighborhood Globe Button, use the tablet's web browser to Share a link, GMail it to yourself, go to your desktop, and pull your mail. If the desktop is on the same Wi-Fi network, the link will work.
(Internally, the top of the reports go into your web browser before the report module finishes generating the bottom parts. Few websites use streaming!)
This sterling example of a Comparison Report is in the External Website section because..
..it has a little 📺 that 🌱 pushes the current Run into the tablet. This allows one to use desktop web tool support to put indexes of related Runs open in many open windows, navigating the tablet easily between them.
~ in the External Website, in App Planar Infinity's Main Activity's Tool Bar:
All Run Indices, in all views, satisfy this view contract:
/. character displays a Run Index without a current Run selected in neon Green:🌱 The Dex will soon feature a leaderboard based on Rank with standard-specific subranks.
Newer versions of the Run Index will have the Section count in the Project line.
💡 You may bookmark a Run Report page, a compare_run_... page, a Project Report, or a
Combined Test Sections Report page, however 💣 the bookmarks only work from inside their
current Wi-Fi intranet.
💡 While Planar Infinity cannot reliably suggest a network name, your network may allow
you to replace the dotted octet notation host number, http://192.168.1.27:8000/, with a real
host name, such as http://GalaxyTabA7:8000/.
🌱 The Globe Button 🌐 raises this website inside the tablet.
Here's a Run Report in the External Website, and
a Run named zone2aisle10 with a 61% Rank:
The Rank is the rote, flat average of a poly Run's multiple Standards' Good assessments. 🌱 The number serves to pool bad Sections while more discriminating numbers determine what to do about them.
A Run with two Arms has two Standard results; one per Arm, averaged together here. A Run with only one Standard result paints its specific Good assessment here.
You are near the top quarter of the documentation.
From here we can go back up ^ to the Domain Objects, ahead to Isopleth Standard, Gap Under Straight Edges, ASTM E1155s, Combined Test Sections Reports, Run Report, Run Index, Mail Menu ...
To merge multiple Runs from different Devices and consolidate their statistical outputs into one set of reports, obtain an Analyst Tablet from AllFlat and mail Project Reports to it.
🌱 Analyst Tablets need no paired Devices; it's okay if they also collect. The determinant is auditability.
Analyst Tablets refine the reports from the field and produce the final manifest for the operation. Also, Section teams themselves should cleanse and assemble their Sections before submitting them to their superior Analyst. A future version of API will scan neighborhoods and detect name mismatches however this one does not. They are simplest to fix early, even if the CTS Report cannot merge two Runs yet.
Tablets with no Runs of their own are Analyst Tablets. If they have no use for the Collect Run Button then it becomes the Import Project Report Button:
💣 The app does not warn on overwrites.
Here's the Intent Chooser in action:
And here's the Import Popup requesting permission to put the reported Runs into the Analyst tablet's database:
An Analyst Tablet should have no Device of its own (conflicting roles) and should only have Guest Projects, with all their Runs etc, from the Device Tablets.
To send the tablet's current state to AllFlat for analysis, or for posterity, tap the AllFlat Logo Menu, and tap System Report. Planar Infinity builds a mail containing the databases and the tablet's recent event log, with internal error messages.
🌱 Remember to add to the mail a brief note explaining why you are sending a System Report, and if it is for archiving or for troubleshooting.
🌱 Mail the database to AllFlat to archive it for posterity, such as before retiring a tablet.
Enviar el estado actual de la tablet a AllFlat para análisis o archivo. Toca el menú del Logo Menu de AllFlat y luego Reporte del Sistema. App Planar Infinity crea un correo con la base de datos y el registro de eventos recientes de la tablet, incluyendo mensajes de error internos, por la mail Intent gateway en GMail.
🌱 Añade una nota breve en el correo explicando por qué si es para archivo ("Analyst") o para solución de problemas o "Troubleshooting."
🌱 Envía la base de datos a AllFlat y los analystas para archivarla, por ejemplo, antes de retirar una tablet.
This form is only for creating new Devices. Adjust nothing here in the field without AllFlat contact.
If you must, tap the Logo Menu button, in the upper left, and tap "Engine" to link a tablet to a Device and configure its permanent Drive settings.
When the form appears for the first time it demands a password; contact AllFlat to learn what it is.
The hardware type has Profileographs and FLIPs, which are two of AllFlat's flagship products.
The Engine Form's hardware type for this device is:
Use the Hardware Type spinner to declare if you intend FLIP Manufacturing.
When manufacturing activates a newborn tablet they always configure the Device first, then the initial Project, in that order.
💡 Some fields let you enter numbers from Android's on-screen keyboard. If a number may be
negative, enter a minus sign - by double-tapping the .- button.
💡 The Engine Form also contains all the fields in the Calibration Form, to set the Device dimensions and calibrate it on the fly during manufacturing.
The form in FLIP mode:
Only change this in the field with AllFlat contact and approval.
Some FLIP devices have pluggable foot pads so Surveyors can configure their step sizes in the field. Manufacturers should select a default foot size, or supply a custom foot size, and then Surveyors can pick the final foot size on the Calibration Form.
💡 Some Standards recommend a Step Size of "300" or "250 millimetres." These logically analyze equally equate to one foot; the math will work the same correctly if all the Devices in a Project use the same size.
This configures the number of Signals that a FLIP device will average to produce a Reading. If the number is large enough, Planar Infinity will trim some extreme signals first.
Set a low number for speed or a high number for accuracy.
Profileographs do not configure this number and always use 5 signals.
Put another way, the Signal Window setting specifies how many individual elevation readings to average together to produce a walking average Reading. Setting a short window will slightly speed up Run collection, and very slightly degrades accuracy, however it won't affect calibration because the FLIP then always uses 16 readings.
The "Spinner" in the upper left displays the host name and network hardware address of each paired Bluetooth device this tablet knows about. If you happen to pair the tablet with your electric toothbrush, then even if it is not in range, its host name and address will appear in the list. Tap the little triangle to pop the list down, and tap the Level Signal Controller host name. Then tap Connect. If this is the first time Planar Infinity has ever connected, the operating system will pop a window up to request permission to connect. Tap "Allow" to continue.
When App Planar Infinity connects to a Level Signal Controller for the first time, and all available Sensors are not set to a valid serial number, the Status Bar will display the type of Bluetooth signal detected, then display the Level Signal Controller's sensors' raw data. Moving the Device arm will change the raw data, providing a hint which sensor is attached to which arm.
💣 Never unpair the Bluetooth because industry security regulations prevent easily establishing the pair.
💣 Your tablet might ask if the Bluetooth pair may access various premium features. The answer is always No.
💣 While App Planar Infinity supports switching a tablet from one Device to another, this is not recommended and may cause confusion. Each Device should use a dedicated tablet.
Tap the Spinner in the upper right to select your hardware type. We support three types:
💡 Some statistical standards call a Very Narrow Aisle a Defined Movement Area, and the opposite a Free Movement area or a Random Traffic Area.
The "FLIP" is typically used with free movement standards such as ASTM E1155 or DIN 18202 that provide absolute elevation. By contrast, Profileographs record relative changes in elevation over their arms' lengths to monitor levelness.
The specifications for some statistical standards use imperial measurements, and some use metrics. 🌱 Planar Infinity can use either measurement units for any statistics system. Leave the Metrics check box unchecked to enter Bases & Step Sizes in inches, and floor sizes & shelf heights in feet. Check the Metrics check box to enter Bases and Step Sizes in millimetres, and floor sizes & shelf heights in metres.
💣 Checking the Metrics check box will not change the entered length numbers. It only changes their underlying units. After changing the check box, remember to edit the measurements, and calibrate & tune the Device.
💣 Although there should be no reason to do this, App Planar Infinity supports changing the Metrics setting during a Project. The analysis will still work correctly (unless the Surveyor changes only the Metrics button, and fails to changes the Bases, or fails to recalibrate).
The Zero Offset, Gain, and Bias always display in inches.
Outputs such as the Run Report display sizes, elevations, & distances using the Device's configured measurement system, and they display statistical input and output using their Standard's preferred measurement system. Grind Tickets display both inches and millimetres to help the grinder operator configure their tools.
Flatness and Levelness Incremental Profilers use App Planar Infinity to walk along a straight Track and survey its profile for Free Movement areas.
Each sensor consists of a foot with two pads — heel & toe — that are typically 12 inches apart. A surveyor rotates between the heel and toe along a straight line to measure "dips" or slopes and calculate an absolute elevation profile.
AllFlat uses the pattern FLIPSN-99999 to name FLIP devices.
Do not use this form in the field because the upper left variables should only change if you are cannibalizing a tablet, and there is no reason to do that.
AllFlat's prototype hardware offering does not have its own documentation yet! We will soon measure entire aisles with multiple arms collecting continous readings.
The number of seconds to wait for the sensor to find a new value. The sensors are slow to be accurate, so they require the device to wait for a positive amount of time before the device should capture readings. AllFlat will provide the sensor's recommended duration.
🌱 Should be between 1.5 and 4 seconds. If the weather is cold, temporarily raise it.
After the seconds expire, a FLIP, detecting walking, collects Signals for from half a second to a second and a half, to average them to create a Reading. The device or surveyor may then opt to capture that Reading as a Step; see the Step Button.
From the Logo Menu, tap the version name to either announce that the latest App Version is installed, or to download it and prompt you with the Downloads or Recents folder to install it.
A FLIP that is out of calibration cannot collect a floor profile that looks relatively flat, so always double-check your profile to see if it makes sense.
Use the internal Edit Run Report to fix the Offset and Bias until Runs tie down. Mathematically, many averages still work like this and err on the side of caution:
We can discard a short Section, or edit to retune only the miscreant Runs and continue. Surveyors should turn off every afflicted Run with the Include Run Check Box or Aggregate Check Box. Re-tune the suspected surveying tool with the Calibration Form and collect a short test Run to ensure the result looks like a floor!
As you start each shift, or if temperature changes, tap the gear icon on the Tool Bar to calibrate the Device, then tap the Zero button. Other calibrations change more rarely.
The FLIP calibration form looks like this, for Zeroing:
💣 If your FLIP Run looks like this you're just out of tune:
💣 Similarly, the maps must pass optical inspection & tuning to boost data integrity. Without Legs and the Isopleth Standard & its client standards
🌱 Usability tip: Serve the website version of your failing section report on a nearby gadget. Using the tablet, we will open the Edit Run Form, adjust the Bias until the miscreant Run looks as close to its neighbors as possible. Each time you bump the current Bias by a small amount, use the gadget's web browser to refresh the page and watch the entire Section reevaluate. (the tablet does all calculations at report time however we are so fast you cannot tell. Except when the Mailer puts up the progress bar.
So each time you change the Bias and refresh the page the Run wil optically tune.
Zeroing measures an Offset to neutralize the tiny angle between a sensor and its Arm. Calibrate at the start of each shift and immediately check the first run for optical flatness before continuing a shift. To get started, open the Calibration Form and tap the Zero Button, launching the Zero Wizard:
Both Profileograph Devices and FLIP Devices calibrate the same way, except the non-FLIP devices calibrate once per Arm, or not at all; their math tunes on the fly.
You have probably already put the device onto a level, marked surface. Tap Next ▶, then
let the wizard wait for the signals to settle and collect a window:
When prompted, rotate the device until its wheels or pads are in the exact opposite orientation and tap Next. The wizard will collect signals again, and then display the new Zero Offset value with the currently detected Reading of the current floor under the Device.
Reverse the Device again, and tap Next ▶. After the wizard collects signals,
The negative of one reading should be within a hundredth of an inch (or millimetre) of the other
reading. This calibration failed because AllFlat personnel were too busy taking screenshots to
operate the device correctly. Use the ◀ Back button to go back to the beginning of the wizard
cycle and try again. Use the Go or Enter button to okay the calibration.
The wizard writes its output into the Zero Offset field, and from now on whenever Planar Infinity calculates an elevation it adds the Zero Offset. This simulates a surveying device with impossibly perfect hardware. Remember after Zeroing all available sensors, and setting their Gain, to Save the configuration so subsequent Runs will use it.
The Zero Offset uses addition and the Gain uses multiplication to tune the hardware. After Zeroing a sensor, tap the Gain Button. The Gain Wizard displays the elevation at the moment it appeared.
Place a shim with a known thickness under one pad or wheel of the hardware device, and observe that the corresponding elevation in the Status Bar goes up. If it goes down, move the shim to the opposite wheel or pad and try again.
Now add the shim's thickness to the captured Reading's elevation, and enter this number. Planar Infinity will calculate the number that multiplies with the captured elevation to produce the expected elevation, and record this as the Gain. The Gain defaults to 1.0, and you cannot enter a Gain of 0.0 because then all elevations would become zero.
🌱 Remember to recalibrate your device each time you would tune a guitar: When you start a day using it, after you adjust its hardware, and after the temperature changes.
If your tablet moves too far away from the Level Signal Controller, this indicator turns gray, and eventually Planar Infinity will refuse to start Runs.
💣 If you begin collecting a Run, then move the tablet too far from the Device, or if you encounter radio noise, Planar Infinity cannot preserve data integrity and will terminate that Run.
From the Tool Bar, tap the Construction emoji to set correct coefficients for the next Run to collect. Analyst Tabletry cannot use this feature.
The Project's community knows which regulatory standards & specs to use, so prepare to select from TR34 FM, EN 15620 Class 400, ASTM E1155, and/or DIN 18202 for a FLIP.
After configuring and calibrating your Device, you raised this form to configure the current Project. It requests many variables. Some only use specific statistics. Its triptych runs from left to right:
💣 There should be no reason to switch Standards in the middle of a Project, though the software technically supports it.
Profileographs may use these Standards:
An early version of the form configured a Run for ACI F-min and DIN 18202 Standards like this:
A graphic below here shows all the fields. Your tablet might have all of them invented so far:
-0.06
The Project, Surface, Section, and Run names will help form filenames (in the mail attachments and website), so they may not contain " ' # Tab ` / ? ! : or % characters. Some platforms make these hard or impossible to type. Surveyors should also avoid other characters they wouldn't want in a filename, such as * $ < > & or excess Spaces.
💣 Remember not to put Space Dash Space, - , into a name because Run file names
use Space Dash Space to separate the names.
Project names are considered unique; Surface names are considered unique to their Project, and Section names are considered unique to their Surface. If you enter the same name twice, the system returns you to that location in the site. When multiple Devices work on the same Project and share their Runs via the ✨ Import Project Report system, remember to manually synchronize the Project Surface and Section names, and keep the Run names unique, because the tablets naturally cannot coordinate them for you. So when using more than one AllFlat device on the same site, hold team meetings every day to 💣 synchronise Project & area names until a new App Version catches up to this problem. Then continue to also manually synchronize anyway.
Planar Infinity uses the Run names and locations to build report filenames. Always use the same Surface and Section names for the same areas in a Site, between Projects, and try to use different Surface and Section names on different Sites.
When making test Runs, such as to tune the hardware, remember to set the Project to "Test" so the Runs don't appear in a legitimate Project's reports. You may also subsequently use the Aggregate Check Box or Include Run Check Box to dismiss unimportant Runs.
In ASTM E1155 theory, the Surface is that group of Sections which share the same construction techniques and hence should mix their statistics. A Project with two different kinds of Surfaces, such as "Slab on Grade" and "Composite Slab," should not average them together because if only one construction technique was suspect then it should not bring the other technique's score down.
In use, configure everything from Project to Section, collect Runs for that Section, then go back to this form and edit the Section to move to the next Section. Repeat for each Surface. If you get a variable wrong, go back to this form, enter the Project, area, and variables you need, and save the form to commit them. The form will retrofit the fields.
If you change the Length and Width without changing the Section name (or higher), Planar Infinity will update the current Section, so make sure this is what you want to do.
You cannot use the Project Form to rename an existing Project or area because we cannot distinguish this action from creating a new record. Use the Edit Run Report and rename existing things.
When using TR34 FM, EN 15620 Class 400, or ASTM E1155 (recommended together), collect Runs on Tracks that strategically criss-cross a Section to provide aggregate statistics. Remember to use the Aggregate Check Box or Include Run Check Box to respect only one Run per Track.
Some Standards use the Section Length, Racking Top Beam Height, and Side Shift settings to recommend or demand various tolerances; others only display them. Some Standards use the Section Length and Width to calculate flatness and levelness averages, and other Standards only display the values.
The ASTM 1155 standard requires a generally correct Section Length and Width. If the Surface has an odd shape, not a rectangle, calculate a proxy Length and Width that multiply together to produce the correct area. The weighted averages use only the area.
This is a failure of levelness in 1155:
If you collect more than one Project on the same Site, such as before and after grinding the floors, remember to make the Surface and Section names the same. A Surface should be all floors in a given building with the same kind of floor, and a Section should be only one pour of that floor. However, the Section name alone should be considered globally, so that if another team visits the same site they must give Sections the same, long, unique name. This helps the Compare Menu select the correct Donor Runs to compare, including Runs from different Projects.
A Profileograph with a drive system will use the Section Length to automatically stop. Remember to either start a Run with a Profileograph's Longitudinal Arm projecting out the entrance to an aisle, or subtract the Longitudinal Base from the Section Length, so the device will correctly stop before the end of the aisle. After the drive stops, if you then tap the Step Button, the drive will attempt to collect another Step.
💣 A Run longer than a mile will hit some internal limits. The developers prefer to leave these bugs in due to our familiarity with short pourable concrete slabs. Landscape and roads use entirely different survey techniques.
💣 The Section Width cannot automatically stop the drive.
🌱 App Planar Infinity supports returning to a previous Project and adding more Runs to it, such as Runs on Surfaces in another building in the same timeframe.
To edit an existing Length or Width, edit the Project Form until all the variables are correct, including the Project, Surface, & Section names, & all statistical coefficients such as Racking Top Beam Height, and Save the form. The correct values will appear in all matching Runs for the current Project.
🌱 If you survey surfaces and then fix them, such as by grinding, start a new Project and only then re-survey them. Otherwise, 💣 App Planar Infinity will mix the statistics together and produce inaccurate numbers.
💣 While Planar Infinity supports Unicode including Emojis in all strings, such as 😃, your desktop might not. Use advanced and recently standardized glyphs with caution.
Use a check box to select at least one statistical standard, and if it has a spinner use it to to select its sub-classes:
If you have a flat open area with Free Movement, use a FLIP with TR34 FM, EN 15620 Class 400, and/or ASTM E1155.
DIN 18202 flags too much slope over various distances.
This is the Project Form with all standards turned on for Free Movement floors:
🌱 Some Standards plagiarize others. Planar Infinity unifies their variables.
The Surveyor must select at least one Standard, and fill its required fields before starting a Run; there is no point to collecting a Run with no Standard.
If you configure a Run and exceed regulatory limits, such as a Run without a Step Size between 250 millimetres and 1 foot, a warning appears in the Project Form.
You may mix and match Standards, but not their sub-classes. You may use TR34 DM with EN 15620 Class 300 (recommended) or with EN 15620 Class 400 (not recommended), but you may not use EN 15620 Classes 300 and 400 at the same time. App Planar Infinity further segregates these classes by hardware type.
Many Standards set limits to floor tolerance and slope that elevations may not exceed, so when you use more than one of them at the same time, App Planar Infinity will enforce the narrowest tolerance and independently the narrowest maximum slope. The system displays the wider tolerances and maximum slopes with a gray background to represent they were "undercut" and not permitted. Look for them in the Preview Panel (above on the right) and in the Run Report.
This Internal Run Report uses ACI F-min and TR34 DM to each undercut the other on different axes of restriction. The narrowest standard always wins:
💣 Planar Infinity supports collecting Runs with different sets of Standards in the same Project, and the reports will. However data hygeine standards in general indicate a one-Project-Per-Standard policy, shared by all devices, reduces the burden of each file's output! Each Project should agree on its Standards before data collection, and to change Standards finish one Project and then start another one.
The Project Form displays the currently selected statistical Standards' elevation and slope tolerances, to help you prepare for them. The Profile Chart displays tolerances as thin horizontal bands, and all statistics appear in the Run Reports.
Defects of Tolerance cause a beep, and their profile line in the Profile Chart will exceed their tolerance band. Defects of Slope cause a beep and a mark, ⬤, colored red or blue, below the Profile Chart. The Run Report contains descriptions of all defects.
Three Levelness Standards calculate Property E — TR34 FM, EN 15620 Class 300, and EN 15620 Class 400. For each Step, Property E is the elevation of the current Step minus the elevation of the Step 3 metres behind it. A negative Property E reveals the floor sloped downwards from there to here. So Property E is the long wavelength detector and Property F is the short wavelength detector, the same as Properties L and F respectively for Levelness and Flatness in other math systems. (And out of order, which breaks the rule that everything appears in the same order everywhere.)
To collect Runs that aggregate Property E, set the name of each Project, Surface and Section, then for each Section collect many Runs on tracks that that are 3 metres apart, first along one axis then across a perpendicular axis. Use the Aggregate Check Box or Include Run Check Box to exclude duplicate Runs on the same Tracks, and make sure all the Runs have the same Project, Surface & Section names. The Run Report will aggregate all Properties E for that Section.
Selecting a checkbox often reveals more configuration controls. Many systems require the Detect Slope Defects Check Box, to indicate whether the Profile Chart and Run Report display Slope Defects. The Edit Run Report, described below, can toggle this flag.
Many systems use these shorthand names for their limits:
When you select a statistical standard, the form calculates its limits for each Arm and displays them so you can prepare for them. These often include:
The industry uses two surveying systems for two purposes:
The construction industry pins another sectors' metric, how wheeled appliances use the floor, to its own sector's categories for the relevant math to ensure safe flatness. Because they are 2 dimensional beasts, a forklift's only metric is whether they circulate on wide areas or straight paths. Surveying the wrong kind of area with an otherwise awesome system produces numbers that are not comparable and might lead to fixing the wrong problems, such as a lump where wheels can't go.
Floors with traffic in any direction, not stuck between Very Narrow Aisles, require absolute elevations measured by FLIP devices.
See TR34 FM, EN 15620 Class 400, ASTM E1155.
The Concrete Society's Technical Report 34 specifies how to measure Free Movement Runs in open areas via TR34 FM.
Its most common field to fill out is the Racking Top Beam Height. Enter it, and the form displays its limits, 🌱 always in millimetres. Taller racks require smoother floors, so their algorithm roughly translates metres of rack into millimetres of floor tolerance.
When the Detect Slope Defects Check Box is turned off, App Planar Infinity hides and ignores d²X and d²Z; the changes in slope over too short an interval.
A Free Movement floor is an arbitrarily wide area where equipment must safely operate while traveling in any direction.
App Planar Infinity analyzes TR34 Free Movement by calculating Property E and Property F, in millimetres.
Property E aggregates differences in elevation, in millimetres, between Steps at least 3 metres apart. TR34 FM sorts all Properties E and finds the one at the 95 percentile. So if there were 302 Steps, all one metre apart, the algorithm samples 100 of them, sorts them, and declares the one at the 95th index to be the P₉₅﹪ ("95th Percentile") for Property E. The algorithm then declares the Run to be out of tolerance if this value exceeds the Maximum P₉₅﹪ Property E. This is why TR34 FM requires a FLIP Base of only 300 millimetres.
For each Step after the first two, Property F measures the amount of incompatible slope over 600 millimetres, so higher absolute numbers are "more uneven." The Run Report will display Properties F at 600 mm intervals.
The report rates Property F, based on how high your shelves are and whether your forklifts have Side Shift equipment.
💡 Properties E and F are absolute values, so a negative is considered equally as extreme as a positive.
App Planar Infinity applies those values to generate a Floor Class from this table:
The standard reports the P₉₅﹪ of Property F, for example:
For a Run with one hundred and two Steps, 94 Steps have a Property F less than or equal to the 95th Percentile, "0.0215" in our example, and 5 Steps are greater than or equal to it. And the first two Steps have an undefined Property F. See Ninety Five Percent.
So a Floor Class of Free Movement 3 must have a Property F 95th Percentile less than 2.2 millimetres. The Run Report displays Property F values greater than the 95th Percentile in orange, and those greater than their FM limit in pink.
Similar to Property E, the Run Report collates all included Runs in a Section and displays a cumulative Property F for all of them.
Runs using some Standards aggregate their Section and Surface statistics in the Combined Test Sections Report.
Runs using Property E and Property F also aggregate their Section statistics in the Run Report:
That means, "For each percentile of Property E, the 95th percent worst one in all readings of Section Pour 7, in the current Project, was 0.25 millimetres out of flatness or levelness." This provides a mathematically neutral way to rank floors from smooth to rough by their most popular results, without worry about whatever rare defect provided a Property E of the 96th% percentile greater.
Why all the 90th% & 95th% everywhere??
It's called Pareto's Law.
Vilfredo Pareto's 1896 observation that 20% of the population owned 80% of Italy's land. This principle, also known as the 80/20 rule, is widely applicable in various fields, from economics and business to personal productivity, by helping to identify and focus on the "vital few" factors that yield the majority of results.
To help the situation, you don't expensively attack the 20% problem; you strengthen as much of the 80% as you can by finding simple ways to do the most good. That applies positive pressure on the remaining problem.
In many other quality, manufacturing, and analytics fields, their 68th, 80th, 90th, or 95th percentiles also form robust & comparable thresholds — balancing sensitivity and aggressiveness. They ignore extreme outliers while focusing on improving their general populations. If the entire system had somehow focused on 91% that would worked too; 90% is mathematically semi-arbitrary, whereas 68.27% is not; it's the Standard Deviation inflection point where a population bell curve switches* from spreading low probability events to concentrating likely events. It is mathematically predestined, and several of the stats here use it.
*This "second derivative crossover point" is Catastrophe Theory. The movie Jurassic Park made everyone think it meant "running away from dinosaurs catastrophically."
Our survey returns wide obvious areas to easily fix, first, and outlying zones to avoid because they might be data mistakes, or the problem might actually be unusual there; then rushing there first might cause mistakes and accidentally make things worse; that's called Churn.
So we practice Measure Twice Cut Once; fixing the easy parts of the floor first, then surveying a few sample Tracks again again to compare their statistics (and profiles) before and after. This avoids overreacting to minor irritations that are not worth fixing due to low odds of recurring in a visibly flattening floor. This improves the odds that fixing the biggest easiest part first of accidentally fixing it anyway with the least effort devoted to it alone instead of the most.
In manufacturing Statistical Process Control, some shops use 80% for their own reasons, and we set the tolerance tighter. Our single-measurement system is not population demographics, so we use 95th%. So our version of Pareto's Law means that efficiently fixing the easiest 95th% of the flatness issues may then incidentally help the remaining hard 5%.
El principio de Vilfredo Pareto, a menudo denominado la regla 80/20, se originó a partir de su observación de la distribución de la riqueza en Italia a finales del siglo XIX. Contrario a la idea de que la economía se centra únicamente en la "fijación de problemas", la revelación original de Pareto era de naturaleza sociológica y agraria: descubrió que el 80% de la tierra en Italia era propiedad del 20% de la población. Esta distribución desigual, que él mismo notó que se replicaba en otros países, no se trataba de una directiva para la gestión de procesos, sino de una constante empírica sobre la concentración de recursos.
La aplicación de esta "constante empírica" a la Estadística de Control de Procesos (SPC) en el contexto de la fabricación y la calidad industrial fue popularizada décadas después por el consultor de gestión Joseph Juran, quien la denominó el Principio de Pareto. Juran postuló que, en muchos sistemas, la gran mayoría de los defectos o problemas (el 80% de las consecuencias) son causados por una minoría de factores (el 20% de las causas), lo que él llamó los "pocos vitales" (Vital Few). Esto permite a los ingenieros enfocarse en la media geométrica de los datos más que en la dispersión total para lograr la mejora de calidad más rentable.
En el gráfico que usted presenta, el Diagrama de Pareto se utiliza para visualizar la frecuencia acumulada de los problemas, donde el 80% de los errores totales se acumula con solo las primeras cuatro o cinco categorías ("Dose missed" hasta "Wrong patient"). El eje secundario y la línea acumulada (la Ogive) son las claves matemáticas: demuestran cómo la suma acumulativa de las frecuencias de los problemas más frecuentes sube bruscamente. Este enfoque de "95/5" que a veces se usa es simplemente una variación más estricta del 80/20, buscando un punto de inflexión donde corregir el 5% de las causas más importantes elimine el 95% de las quejas, forzando una intervención quirúrgica en el sistema de producción.
La Desviación Estándar es la medida de la cantidad de variación o dispersión de un conjunto de valores.
La importancia de esta herramienta, el diagrama de Pareto, radica en su capacidad para reorientar las estrategias de corrección de fallos, alejándonos de la "tiranía de los muchos triviales" (Trivial Many). En lugar de dispersar recursos atacando las doce categorías menos frecuentes de la derecha (como "Technique error" o "Unauthorized drug"), el equipo debe invertir el tiempo de desarrollo y pruebas únicamente en los pocos problemas de alta frecuencia de la izquierda. Esta jerarquización de los fallos, basada en el impacto que tienen en la frecuencia total, asegura que las intervenciones generen el máximo retorno de la inversión (ROI) en términos de calidad y estabilidad operativa de su fleet de dispositivos.
These diagrams illustrate how Pareto charts separate “vital few” from “trivial many”; how percentile curves behave (e.g. how much of data lies under the 95 % mark), and how Lean/SPC methods formalize the idea of focusing effort where it yields outsized gains. In our context, combining Pareto reasoning (fix what’s big and easy first) with the 95th percentile metric gives you a defensible analytic filter—fix the bulk first, let the tails be.
So the industry uses Pareto's Law to determine what not to fix first. This sounds like a good ideology that you should do, right? The number 95th% appears at junctures that already force you to do it.
As mentioned, after each grind, re-collect a few known Tracks with fresh Runs and use Before And After Grinding to compare the ground-down profile, to make sure progress moves in the correct direction.
Note that a Property E or F passes if small, and a L or F (F-min or FF/FL) passes if large. They are still scalar ratings. Using an ascending rage factor is convenient in some operations, and using the reciprocal of an arbitrary* unit of flatness achievement is motivating.
*The F-min, FF, and FL units are known; they are just not worth writing down or ever using for comparisons with any physically measured units ever except themselves.
The point of all this math is so each kind of floor number, E, F, L, is globally comparable between its own kind, E, F, L, from different systems of survey tools using different data collection techniques on the same floor. Each used the same Standard formulas so all the devices will rank those floors in the same order from worst to best (or best to worst) using freely comparable numbers. 95th% is one of the force multipliers that amplifies such a signal as another tool perforce agree with. That's literally why so many different P95th% factors installed everywhere; so each of their weighted averages force unwitting obedience to Pareto's Law.
🌱 💣 Therefore, in a report, two 95th% symbols right next to each other might mean different counted objects, different scalar units, different types of scalar unit, or even entirely different formulas. Quite a few other kinds of symbols share this honor too; they might still accidentally compare apples and oranges right next to each other so check the types and context.
68th% or 95th% is just a common handy number to narrow Pareto's Law when the topic is indeed one floor; one demographic variable instead of all of Italy, with many variables, at 80%. We discard the outliers because they could be collection mistakes or because fixing them first adds risk.
Europe's version of TR34 applies standard deviations to the properties that TR34 averages and partitions by severity, so the two systems complement each other's system to isolate problem Sections.
It adds 𓉭 EN 15620 Class 200 for robotic aisles with rails requiring further long-distance attention. Defined Movement areas pass 𓉱 EN 15620 Class 300, and spacious Free Movement Sections submit to 𓉪 EN 15620 Class 400.
This is for absolute elevation over Very Narrow Aisles for railed or automated forklifts
The BS EN 15620:2008 Standard specifies pallet racking tolerances. Class 200 finds long slope defects in special aisles such as with robotic forklifts on rails. Floors with a Section Length up to 150 metres long must be within 15 millimetres overall tolerance, and over 250 metres must be within 20 millimetres tolerance, with intermediate floors prorated between these limits.
This statistical Standard only uses the Section Length, to calculate its Tolerance.
Finds average defects in Free Movement areas, measured with FLIP devices providing absolute elevation, wide enough for any equipment to safely turn around.
These statistics require the Racking Top Beam Height to determine how narrow to make the Tolerances, and Detect Slope Defects Check Box turns on the Maximum Slope detection. If the forklifts will use a Side Shift arm, they enforce wider limits.
The ASTM International E1155 document provides math formulae to accumulate many elevation Readings, from Runs on many Tracks over a Section, into overall weighted averages of floor flatness and levelness. Higher F numbers, as always, are more flat and level.
"Floor Flatness" rates how few bumps interrupt a floor's smoothness, and "Floor Levelness" rates how closely a floor follows a perfectly horizontal grade. Put another way, a low "Flatness" rating detects waves with one foot wavelengths, and a low "Levelness" rating detects waves with ten foot wavelengths.
That is a FLIP running App Planar Infinity measuring a garage floor designed to shed liquids, so it failed its Levelness check with 4.51. The numbers are too low. (Other floor measuring devices rate this floor at 20.32 flatness and 4.72 levelness, and any survey performed twice will always change the low significance digits such as .66 and .51.)
The goal of the 1155 Standard is to rate each floor with a flatness rating (or a levelness
rating) such as 76.54 ‹55.90 – 97.18›, where the floor's average flatness is 76,
and 9 out of 10 new flatness readings within that floor are predicted to land between
56 and 97 flatness. The ranged numbers are therefor the "flatness 90th% confidence interval."
As usual, the higher the number, the flatter or more level the floor.
The ASTM E1155 standard requires these 'specs' or 'specifications':
To disregard a limit, set it to zero 0, and interpret this as "any amount of roughness is permitted."
All Surfaces in a Project obey the same values. If you collect Runs and then update the values, the old Runs use the current Project values. If you get the limits wrong for a Project, go to the Edit Run Report or Edit Combined Test Section Report and change the numbers. They will update for the whole project.
Projects with 1155 Runs produce weighted averages of all included Runs for each Section:
Section Statistics which fail their Project's Specified Overall limits are pink, and Run statistics which fail their Project's Minimum Local limits are pink in their backgrounds.
(This report comes from an automated test, so the Device names are "Sally Goodin," "Guest," or "Guest2" to spike them as not real data.)
Note that Runs within a Section are sorted in the order they were collected.
💣 The surveyor did not set the Section Length and Width correctly, so the weighted averages are slightly wrong. The surveyor can use the Edit Run Report to correct them.
The Deutsches Institut für Normung ("German Institute for Standardization") General Building Specification 18202 limits how much a floor may slope over various distances. Any device type may use it to detect flaws in flatness or levelness. (DIN is also useful to select a Standard that requires limited input, similar to GUSE, such as to qualify for the Grid Map and not use Isopleth.) 🌱 This is also therefor the parking Standard for using the 𓊊 Grid Map ～ in Metrics mode because € ～ yet with no other F nonsense in the way for those who desire to feed the insatiable 𓊊 Section Popup Grid. It will make the Combined Test Sections Report Section Panel Run List very narrow to leave more room for the Grid!
We target "Group 4," for more strict requirements, leading to these tolerances:
If the Step Size cannot be 1 or 0.5 metre (if, for example, you use a FLIP with a fixed foot Base of 12 inches), Planar Infinity will round the distances up to the next Step. This slightly widens the tolerance.
This statistical standard requires no input on the Project Form.
The Run Report produces this table (the Profileograph's Longitudinal Arm colored it red):
Interpret the line "1.219 .. 74 .. 74.0 .. 18.09 .. 3 .. 97%" like this:
Among all the 1.219 metre intervals between Steps, the largest disagreement of elevation, Maximum Difference, was 18.09 millimetres. This occurred 74.0 Distance Feet into the Run's Track, on the 74th Step (compared to the Step 4 feet closer to the beginning of the Run's Track). The difference in elevation exceeded the standard Limit mm of 3 millimetres, so it is pink. And for all such 1.219 metre intervals between Steps, 97% of their differences in elevation were narrower than this limit. Because some Steps failed, the Good percent field has a pink highlight.
The Run Report's Results table lists all the Steps who failed their limit checks.
aka
The point of a recurring pattern of very simple analytes over a 3m grid surface is to collect a reference across many floors for comparison, and to look for bumps in output charts.
App Planar Infinity finds deviations in flatness called Gaps (huecos), when the Project Form checks the ✅ GUSE Standard and fills out the Straight Edge Length & Maximum Allowed Gap. Its new standard GUSE simulates laying a straight edge of a given length on the floor and measuring the gaps underneath to find the largest one, then displaying the top two or three gaps of all such placements of the straight edge along the Run's track.
In math terms, the algorithm finds a walking convex hull over the floor's profile, and its three most serious deviations.
App Planar Infinity busca huecos (Gaps), con ✅ GUSE checked y Straight Edge Length y Maximum Allowed Gap establecido correctamente en el formulario del proyecto Project Form. Este estándar nuevo GUSE tiene una función que simula colocar una regla recta de una longitud dada en el suelo y medir los huecos debajo para encontrar el mayor de ellos, y luego mostrar los dos o tres huecos más grandes de todas las posiciones posibles de la regla a lo largo de la trayectoria del recorrido.
En términos matemáticos, el algoritmo encuentra una envolvente convexa móvil sobre el perfil del suelo y sus tres desviaciones más significativas.
See the Project Form to set the GUSE check box to get Gap Under Straight Edge. The output looks a little bit like this:
That un-tuned Run has three random Gaps. Interpret (From 2 At 15 To 42) Gap: 0.042042 to mean
"A Gap at Step 15 under a Straight Edge from Step 2 to 42." If the Gap instead says "Gap: 0.420420 (0.29542)"
then your Gap exceeds the Maximum Allowed Gap by (that) much.
Use the Edit Run Report to set the Straight Edge Length shorter for more Gaps.
💡 Note that Maximum Allowed Gap is helpful and will supply an eighth of an inch, or 3 mm, if the user forgets.
💣 The next version of App Planar Infinity has a mysterious bug somewhere in the HTML view layer where the Straight Edge Length and Maximum Allowed Gap editors appear in the Edit Run Report of non-GUSE Runs. Changing their values converts the Runs into GUSE Runs. We have a team of international multidisciplinary experts working around the clock and living on donuts to determine in what layer of the application this bug may reside. Until then, they collect danger pay, so be advised that editing the fields will have a slight, low-percentage chance of adding the standard Gap Under Straight Edge to a legacy Run that did not collect with it. But the odds are somehow greater for FLIP Runs.
AllFlat's house Standard borrows the best of the 3m survey standards to generate a contour diagram. Surveyors with less than a rabid interest in contours may also use this Standard and apply their own tolerances. So either way the Standard helps anyone who needs to correct floors first and study the deep numbers later.
Standards such as GUSE, TR34 FM, and EN 15620 Free Movement — using available resources to coach the user to walk their FLIPs in the correct pattern to paint a Heat Map describing floor elevations. The 3m survey super-standard specification generates a Grid Map and interpolates intermediate elevations.
All Contours move the Runs up or down so their relative origin links to the common origin in the section's southwest corner. Without the Isopleth standard, the Run Results table uses the Run's local relative origin, and the re-leveled Run Results table appears inside the Combined Test Sections Report and the Section Popup. With the Isopleth Standard, the Run Results are always releveled and do not appear redundantly in the CTS Report.
Note that geology surveyors call this a "contour," and the industry calls its drawing a Heat Map (hence "isotherm") because low elevations are cool blue and high is hot red. Algorithmically, a Map is an unfinished Isopleth that still contains useful data.
Iso means same and pleth means layer; like plywood.
🌱 This is one of the outputs that must optically "look like a floor" to pass muster. Remember that some incorrectly collected sections still have normal-looking averages, so always visually inspect the map while confirming that a complete Section is in the database.
Some industry leaders pronounce contour "autostore," which factually refers to modern floors
for robotized rail forklifts, which are literally and figuratively only tangentially related.
When such Runs use the Isopleth Standard, their Run Result tables and elevations in the Profile Chart use their new relative origins; not their standard profile origins at 0.0.
💣 This Standard conflicts with ASTM E1155 because its math requires a relative origin of 0.0 for each Run. If you turn off Isopleth Standard and still have legs then Grid Map will still work, however the chart profiles and Run Results will display their relative origins at 0.0. The fix is to run the reports twice; once with 1155 and without legs, and again without 1155 and with legs. A future version will automate this workaround.
The correct winding always starts with an origin in the "southwest" corner and proceeding counterclockwise only. You may use four little legs or one big marathon loop:
You may collect the legs and internal Runs in any order so long as their orientations and numbers match that pattern. However that diagram shows the best marching order to make every huge Section the same for you: Do the perimeter first, check the map, and repeat until the map grows a full contour.
The Legs must wind counterclockwise. If an internal Run uses an alternate direction, such as 2EW, the the Grid Map can fix the Run because it relies on the legs using the correct orientation.
💡 Collect the outermost Legs First so the 𓊊 Section Popup can always display progress filling in the map.
That forms a counterclockwise circuit of Bias Runs, but only if they are named
with variations like leg3ew, bias3ew, etc.
App Planar Infinity uses all four legs to return to the origin, detect the bias between the final step and absolute zero, and use that bias to raise or lower the legs. This means leg Runs are Bias Runs, however they cannot be the kind of independent Bias Runs that go out and back to the same point. App Planar Infinity must use the end point of one leg to match the start point of the next leg.
After biasing the legs, the Grid Map raises or lowers the internal Runs to fix their elevations relative to the absolute origin in the southwest corner.
See ☰ Run Index
The list of Projects and Runs appears in several contexts including published and in segments in the Project Index in the mail.
For a tablet, the gray button in the center of the Tool Bar, near the current Run's datetime, raises the internal Run Index. (The latest App Versions put the most recent Project at the top.) The Internal Run Index shares contents with the Project Index and the External Website's Run Index.
The index highlights the currently viewed Run in green. This explains why that Run has no ⚖️ icons; because you cannot compare a Run with itself. Un-included Run names are gray.
The Run Index categorizes Runs in their areas; Projects, Surfaces, and Sections. Tap a Project name to open or close its list of Runs, with their summary data, and tap a Run to select it for examination in the Profile Chart, Reports, and Mail.
This is from the External Website pages, and it applies to all Run Indices:
The Runs are grouped by Surface and Section, and sorted by collection time, with the most recent Run at the bottom.
🌱 Collect the Runs in the order you want them to appear in the list.
💡 After you view a Run and open a Run Report, the hamburger ☰ icon switches the report to the Run Index.
See Comparisons:
Tap the Report button 🗒️ to raise the Run Report inside App Planar Infinity.
💡 The tablet's Back Button closes reports and the Run Index etc.
🌱 The internal reports might exceed the screen size, so pinch or swipe the screen to resize or scroll them.
This report contains all the data used to calculate one Run's statistics, including the Device type and dimensions, its calibration, its Project settings, the date & time of the Steps, each captured Reading's elevations, their statistical outputs, and their marks & annotations.
Because many values are trivial (such as the Zero Offset) or redundant (such as the
Drive Powers), they are hidden. Scroll down and tap the ▸ Details button to display them.
The Internal Run Report (and Internal Run Index, and Combined Test Sections Report) are interactive and can perform simple edits such as renaming some text values, fixing wayward elevations, or setting the Run Length.
🌱 The only reason to change things should be to avoid redoing the entire Run if it's the most representative one.
To change values, tap the 🔒 button. Rename-able values display a gray underline & a pencil-on-paper button, and controls like Include Run Check Box or Aggregate Check Box also become available. And many fields can accept modest edits to clean up if someone made a mistake entering site information in the field. The goal is all site area names are as consistent as possible for a series of Projects, while minimizing reasons to re-collect another Run on the same Track.
Tap the edit pencils, and a Rename Requester pops up. Edit the name and tap the "Change" button; Planar Infinity updates the database and the displayed report.
The standard Project Form and Collect Run Requester rules for text names still apply, including uniqueness, forbidden characters, and ill-advised characters.
💡 You may use the Rename Requester to change a name's case; from lower case to upper case, for example.
💡 You may only rename a Project, Surface, or Section relative to the current Run. To move many Runs to a different Section, for example, you must open each Run and rename its Section.
💣 You may not rename optional items like the Address or Telephone number; you may not rename the Surveyor, and you may not change anything while collecting a Run.
Future releases of App Planar Infinity let users fix a mistake setting the Standards at qRun start time.
Sometimes Surveyors start Runs with incomplete information. If the Project's obligations change the collected Run record must change with it because the recorded numbers don't care WHY they were recorded. So, for example, if a Run collected with ASTM E1155 but its community subsequently determined it also needed Gap Under Straight Edge, then the Surveyor can open the internal Run Report, unlock it to summon the Edit Run Report, and tap on the GUSE checkbox.
The Internal Run Report in unlocked Edit Run Report mode can adjust all the Section Lengths and Widths for all of this specific Section's Runs: