<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Getting Started — GeoSC Documentation</title>
    <link>/getting-started/index.html</link>
    <description></description>
    <generator>Hugo</generator>
    <language>en-gb</language>
    <atom:link href="/getting-started/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Concepts and Workflow</title>
      <link>/getting-started/concepts-and-workflow/index.html</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/getting-started/concepts-and-workflow/index.html</guid>
      <description>GeoSC separates design questions that are often blurred together.&#xA;Stage Question Main artefact Important limit Power Could the proposed design detect effects on the tested grid under the fitted simulation DGP? power_analysis_results.csv It does not forecast campaign lift or establish identification. Donors Which eligible geographies have useful pairwise pre-period similarity to each treated geography? donor_eval_results.csv Recommendations and selected_weight are screening outputs, not fitted SparseSC weights. Inference How did treated outcomes differ from the SparseSC counterfactual during the measurement period? geolift_results.json Causal interpretation remains conditional on design assumptions. In GeoSC, a control is a geography not assigned treatment in the input to a stage. A donor is a control geography eligible to contribute to a synthetic counterfactual. Operationally, analysts often use the words interchangeably, but eligibility should be determined before model fitting.</description>
    </item>
    <item>
      <title>First Successful Run</title>
      <link>/getting-started/first-successful-run/index.html</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/getting-started/first-successful-run/index.html</guid>
      <description>This run checks the installed CLI and artefact path using the source checkout’s synthetic data. It is a software smoke test, not evidence that the demo is a credible client design.&#xA;geosc infer \ --config data-config/geolift_analysis_config.yaml \ --no-create-plots A successful command returns exit code 0 and writes these files under the configured inference output directory:&#xA;geolift_results.json; geolift_diagnostics.json; data_validation.json; assumption_validation.json. Inspect them in this order:&#xA;data_validation.json: confirm the panel, periods, units, and data policies. geolift_results.json: require status: &#34;ok&#34; or investigate every warning on a partial result. Never report a failed result. geolift_diagnostics.json: review pre-period fit, placebo support, and donor weight concentration. assumption_validation.json: distinguish the gate-eligible parallel-trends diagnostic from the advisory interference screen. Next, replace the demo config with a copy tied to your panel. Follow Prepare an Input Panel before using client data.</description>
    </item>
    <item>
      <title>Installation</title>
      <link>/getting-started/installation/index.html</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/getting-started/installation/index.html</guid>
      <description>GeoSC 0.3.0 supports Python 3.10 to 3.13. Use an isolated virtual environment.&#xA;Install a maintained build python -m venv .venv source .venv/bin/activate python -m pip install --upgrade pip python -m pip install /path/to/geosc-0.3.0-py3-none-any.whl geosc --help The build installs both geosc and the compatibility command geolift. It does not include the repository’s data-config/, recipes/, or shapemap/ directories. Supply your own input CSV and YAML files.</description>
    </item>
  </channel>
</rss>