Skip to main content

Documentation Index

Fetch the complete documentation index at: https://mintlify.com/acdeveloper-sci/fortriage/llms.txt

Use this file to discover all available pages before exploring further.

ForTriage provides two ways to upload Fortran source files before running analysis. Both mechanisms are available from the Overview tab’s upload area. Files are staged in memory for the duration of the session — nothing is written to disk permanently.

​
Allowed file types

ForTriage accepts files with the following Fortran source extensions:
  • .f — fixed-form Fortran
  • .f90 — free-form Fortran 90
  • .f95 — free-form Fortran 95
  • .for — fixed-form (common alternative extension)
  • .fpp — Fortran preprocessor source
The per-file size limit is 200 MB.
Most Fortran source files are kilobytes to low megabytes in size — well under the 200 MB per-file cap. You are unlikely to encounter this limit unless a single file contains generated or machine-expanded code.
Files with any other extension — including .f77, .mod, or plain text files — are ignored during extraction. If you upload a ZIP, only Fortran files inside it are staged; all other archive members are silently skipped.

​
Direct file selection

Use the “Upload Fortran source files” uploader at the top of the Overview tab to select one or more Fortran source files from your local machine. You can select multiple files in a single dialog by holding Ctrl (Windows / Linux) or ⌘ (macOS) while clicking.
Browser-selected files carry only a filename — there is no folder path attached. If you select two files named calc.f90 from different directories, ForTriage cannot tell them apart. The first file uploaded with a given name is kept; subsequent files with the same name are rejected and a warning is shown. If you need to upload same-named files from different subdirectories, use the ZIP archive mechanism instead.
Files uploaded directly appear immediately in the staged file list below the uploaders. To remove a directly-uploaded file, use the native ✕ control on the file uploader widget itself.

​
ZIP archive upload

Use the “Or upload a .zip archive” uploader to supply a single .zip file containing any number of Fortran sources. Subfolder structure is fully preserved. An archive containing both modulo_a/calc.f90 and modulo_b/calc.f90 stages both files as distinct entries — they are never flattened to a shared basename. This is the recommended mechanism when your codebase is organized into subdirectories. Additional details about ZIP handling:
  • Only files whose extension matches the allowed list are extracted; all other archive members are ignored.
  • Files inside the ZIP that exceed 200 MB are skipped and listed in a warning banner.
  • Zip-slip protection is enforced: any entry whose path resolves outside the archive root (e.g. ../../etc/evil.f90, or an absolute path) is automatically rejected. No traversal paths are ever staged.
  • Two files in the ZIP that share a basename but live in different subdirectories are both staged. However, a warning is shown because the File column in Forti4D’s output reports only the basename — results for same-named files across folders may be hard to distinguish in the report view.
If a directly-uploaded file and a ZIP entry share the same name, the directly-uploaded file wins. Direct files are registered first; ZIP entries are only added for names not already present in the staged list.

​
Staged file list

After uploading, each staged file appears as a chip below the uploaders, showing its name (including subfolder path for ZIP-sourced files).
  • ZIP-sourced chips have an × button. Clicking it removes that individual file from the staged list without re-uploading the archive.
  • Direct-sourced chips do not have a remove button — use the native file uploader control to deselect those files.
  • The 🗑️ Clear all button in the top-right corner removes every staged file and resets both upload areas to their empty state.

​
Running the analysis

Once your files are staged, click Run analysis to begin.
1

Select files

Use one or both uploaders to stage your Fortran sources. Review the chip list to confirm the correct files are present.
2

Review the staged list

Check for any warnings about duplicate filenames, oversized entries, or large corpus size. Address them if needed, or proceed.
3

Click Run analysis

Click the Run analysis button. The button is disabled while an analysis is already in progress. If no files are staged, an error is shown instead of starting the run.
If the total size of all staged files exceeds 6 MB, a non-blocking advisory warning appears before you click:
“Large corpus detected — analysis may take longer than usual.”
This warning does not block analysis — it is purely informational.
AI Insights privacy: after every run, ForTriage automatically sends aggregated metrics about your code — not raw source — to Google’s free-tier Gemini API. Google may use submitted content to improve its products. If your codebase is confidential, review Google’s data terms before proceeding. See AI Insights privacy for details.

Build docs developers (and LLMs) love

Get started for freeTalk to us