4. Web Application

The pyCSAMT web application is a browser-based studio for CSAMT, AMT, and MT survey work. It runs the same scientific package as the Python API and the desktop GUI, but presents it as a single-page Dash/Plotly application that you open in a web browser. Use it to load EDI data, inspect maps and profiles, run quality control, preview and apply corrections, produce advanced diagnostics, build forward and inversion models, browse inversion results, and drive the pyCSAMT agents — all without writing code.

The web app is not a separate science layer. Its callbacks delegate to the same pycsamt.app.desktop.controllers used by the desktop GUI, so a survey loaded here behaves exactly as it would in the desktop app or in plain Python. What differs is the working style: the web app is built for shared servers, team demonstrations, and cross-platform access from a browser.

An animated tour of the web studio: welcome, load a survey, inspect the interactive station map and profile pseudosections, run quality control and corrections, run an AI-assisted inversion, and view the 3-D resistivity scene. Each surface is documented on the pages below.

A good first pass, in order, is Overview → Installation → Navigation → Loading & Sessions → Maps & Profiles → Processing Pages → Exports → Deployment → Troubleshooting.

• 4.1. Overview
  • 4.1.1. When To Use The Web App
  • 4.1.2. Run The Web App
  • 4.1.3. Navigation Map
  • 4.1.4. Main Concepts
  • 4.1.5. Screenshots
• 4.2. Installation And Launch
  • 4.2.1. Install The App Extra
  • 4.2.2. Launch The Web App
  • 4.2.3. The Welcome Screen
  • 4.2.4. Command-Line Options
  • 4.2.5. Examples
  • 4.2.6. Verify The Launch
  • 4.2.7. Next Steps
• 4.3. Navigation And Layout
  • 4.3.1. The App Shell
  • 4.3.2. The Command Bar
  • 4.3.3. The Navigation Rail
  • 4.3.4. The Home Dashboard
  • 4.3.5. Theme
  • 4.3.6. Settings Drawer
  • 4.3.7. Help / About
  • 4.3.8. Differences From The Desktop GUI
  • 4.3.9. Next Steps
• 4.4. Loading Data And Sessions
  • 4.4.1. Loading A Survey
  • 4.4.2. Adding Lines To An Existing Survey
  • 4.4.3. Managing Survey Lines
  • 4.4.4. Recomputing Transfer Functions
  • 4.4.5. Browser Sessions
  • 4.4.6. Data Health After Loading
  • 4.4.7. Next Steps
• 4.5. Maps And Profiles
  • 4.5.1. Recommended Inspection Order
  • 4.5.2. Map View
  • 4.5.3. Profile View
  • 4.5.4. Phase Tensor Pseudosection
  • 4.5.5. 3D Map
  • 4.5.6. Figure Export And Code Parity
  • 4.5.7. Common Issues
  • 4.5.8. Next Steps
• 4.6. Processing Pages
  • 4.6.1. Shared Controls
  • 4.6.2. Quality Control
  • 4.6.3. Correction
  • 4.6.4. Advanced Plots
  • 4.6.5. TDEM
  • 4.6.6. Processing Pipeline
  • 4.6.7. Forward Modelling
  • 4.6.8. Inversion
  • 4.6.9. Results View
  • 4.6.10. Interpretation
  • 4.6.11. AI Agents
  • 4.6.12. Tools
  • 4.6.13. How Pages Delegate To The Package
  • 4.6.14. Next Steps
• 4.7. Exports And Reproducibility
  • 4.7.1. Saving Figures
  • 4.7.2. Page And Tool Exports
  • 4.7.3. Batch Export
  • 4.7.4. Session Files
  • 4.7.5. Reproducing Web Output In Python
  • 4.7.6. Practical Export Habits
  • 4.7.7. Next Steps
• 4.8. Deployment Notes
  • 4.8.1. Local-Only (Default)
  • 4.8.2. Internal-Network Access
  • 4.8.3. Choosing A Port
  • 4.8.4. Behind A Reverse Proxy
  • 4.8.5. Cache And Temporary Files
  • 4.8.6. Where State Lives
  • 4.8.7. Security Expectations
  • 4.8.8. Framework
  • 4.8.9. Next Steps
• 4.9. Troubleshooting
  • 4.9.1. Launch Problems
  • 4.9.2. Loading Problems
  • 4.9.3. Page And Callback Problems
  • 4.9.4. Plotting Problems
  • 4.9.5. Agent Problems
  • 4.9.6. Browser Problems
  • 4.9.7. When To Use Debug Mode
  • 4.9.8. Still Stuck?