Verification Test Suite

After running the automatic installer, you should verify the integrity of the installation, environment variables, and connection to the licensing system before launching large production runs.

1. Environment Check

Ensure the following variables are defined in your current environment. If you just installed the suite, make sure you have reloaded your terminal configuration (source ~/.bashrc):

echo $SHARDIAN_API_KEY
echo $LD_LIBRARY_PATH

SHARDIAN_API_KEY must print your active licensing key (e.g. sk_live_shardian_...).
LD_LIBRARY_PATH must include the path where the dynamic libraries were installed (usually /usr/local/lib or ~/.shardian/lib).

2. Testing License Server Connectivity

You can test connectivity to the Shardian API server and key validation directly from the command line using curl:

curl -i -H "Authorization: Bearer $SHARDIAN_API_KEY" https://api.shardian.com/v1/verify

Successful Response:

The server will return an HTTP 200 OK status with a JSON body confirming key validity:

HTTP/1.1 200 OK
Content-Type: application/json
Date: Mon, 15 Jun 2026 12:00:00 GMT

{
  "status": "valid",
  "key": "sk_live_shardian_cfd_atmos_2026_eval",
  "scope": "both",
  "expires_at": "2027-06-15T00:00:00Z"
}

Failure Responses:

HTTP 401 Unauthorized: The key is incorrect or has been revoked. Check that your environment variable matches the exact key provided by support.
HTTP 403 Forbidden: The key is valid, but the product scope does not cover the requested simulation (e.g., trying to run WRF with an Aero-only key).
Network Timeout: If curl hangs, you are likely behind a restrictive corporate firewall. Please refer to Licensing & Network Errors to configure your system proxies.

3. Verifying Shardian Aero (OpenFOAM)

To verify that OpenFOAM can dynamically load the Shardian Aero library:

Run the following command to check if OpenFOAM lists the custom boundary conditions and models from the dynamic library:
```
simpleFoam -postProcess -libs "libShardianAero.so" -help
```
If the library loads successfully, the command will complete without library errors. If the file libShardianAero.so is missing from LD_LIBRARY_PATH, OpenFOAM will throw a dynamic loading error:
```
Error: cannot open shared object file: No such file or directory
```
If this happens, check that /usr/local/lib/libShardianAero.so (or your user path) exists and is readable.

4. Verifying Shardian Atmos (WRF)

To verify that the Singularity container is operational and can access the host MPI libraries:

Run the global wrapper command:

shardian_atmos --version

Alternatively, call the container directly:

singularity run /usr/local/bin/shardian_atmos.sif --version

The output should display the container release version, the compiled WRF version, and confirmation of OpenMPI bindings:
```
Shardian Atmos Solver Container v1.0.4
Compiled with WRFV4.5.1 (Intel compilers)
OpenMPI Binding: v4.1.2 compatible
```
If you receive permission denied errors when running the container, check file permissions:
```
ls -l /usr/local/bin/shardian_atmos.sif
```
If necessary, apply read and execute permissions:
```
sudo chmod 755 /usr/local/bin/shardian_atmos.sif
```