LaconicNetwork/lockdrop-simulation
9
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases 1 Wiki Activity

Add steps to tunnel jupyter server endpoint

Browse Source
This commit is contained in:
Prathamesh Musale 2025-08-18 20:27:53 +05:30
parent 8faee524f0
commit 27b3e7e975
3 changed files with 19 additions and 9 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

13
EXPERIMENT.md
View File

@ -37,12 +37,19 @@ This guide explains how to use the interactive notebook to experiment with diffe
This script will:
- Automatically create a Python virtual environment
- Install all required dependencies
- Launch Jupyter notebook with the experimentation interface
- Open your browser to the interactive notebook
- Automatically launch the Jupyter notebook with the experimentation interface in you browser
If jupyter is running on a remote host, you can tunnel the port `8888` to load the notebook in your local browser:
```bash
ssh <user>@<control-node-ip> -L localhost:8888:localhost:8888 -Nv
```
Open the URL from server logs and load `lockdrop-calculations.ipynb`
3. **Use the Interactive Interface**
The notebook will open automatically in your browser. Execute it by clicking "Run All Cells" from `Run` tab in order to start experimenting with different participation scenarios.
Once the notebook has been opened in your browser, execute it by clicking "Run All Cells" from `Run` tab in order to start experimenting with different participation scenarios.
## Using the Interactive Interface

6
README.md
View File

@ -120,7 +120,7 @@ The lockdrop simulation validates the Zenith Network's token distribution mechan
ZENITH_STACK_DIR=$(pwd)/zenith-stack
# Checkout to the required version
cd zenith-stack
cd $ZENITH_STACK_DIR
git checkout $ZENITH_STACK_VERSION
```
@ -226,13 +226,13 @@ It allows flexible simulation parameters:
**Bootstrap Validator Configuration**
- **Bootstrap validator data directory**: Absolute path to the parent directory where the bootstrap validator deployment will be created (use the same parent directory as set for Genesis Generator).
- **Bootstrap validator data directory**: Absolute path to the parent directory where the bootstrap validator deployment will be created (**use the same parent directory as set for Genesis Generator**).
- **Validator display name (moniker)**: Human-readable validator name for the simulation (default: ZodNode).
**Gentx Signer Configuration**
- **Gentx signer data directory**: Absolute path to the parent directory where gentx will be signed and the genesis file created (use the same parent directory as set for Genesis Generator).
- **Gentx signer data directory**: Absolute path to the parent directory where gentx will be signed and the genesis file created (**use the same parent directory as set for Genesis Generator**).
### View Configuration

9
test-runs/README.md
View File

@ -87,7 +87,7 @@ To reproduce the results from any one of the test runs, follow these steps to ru
ZENITH_STACK_DIR=$(pwd)/zenith-stack
# Checkout to the required version
cd zenith-stack
cd $ZENITH_STACK_DIR
git checkout $ZENITH_STACK_VERSION
```
@ -190,13 +190,13 @@ This interactive tool will guide you through configuring all the necessary varia
**Bootstrap Validator Configuration**
- **Bootstrap validator data directory**: Absolute path to the parent directory where the bootstrap validator deployment will be created (use the same parent directory as set for Genesis Generator).
- **Bootstrap validator data directory**: Absolute path to the parent directory where the bootstrap validator deployment will be created (**use the same parent directory as set for Genesis Generator**).
- **Validator display name (moniker)**: Human-readable validator name for the simulation (default: ZodNode).
**Gentx Signer Configuration**
- **Gentx signer data directory**: Absolute path to the parent directory where gentx will be signed and the genesis file created (use the same parent directory as set for Genesis Generator).
- **Gentx signer data directory**: Absolute path to the parent directory where gentx will be signed and the genesis file created (**use the same parent directory as set for Genesis Generator**).
### View Configuration
@ -256,6 +256,9 @@ Copy the generated folder from your chosen test run to zenith-stack:
# Navigate to the lockdrop-simulation repo directory
cd $LOCKDROP_SIMULATION_DIR
# Remove any existing data from previous runs
rm -rf $ZENITH_STACK_DIR/generated
# Example for run1
cp -r ./test-runs/run1/generated $ZENITH_STACK_DIR/generated