Tab-separated table
Use one header row. CSV is accepted for prediction, but TSV remains the workflow default.
[ai/ml online workbench]
A Matrix-native interface for FNN regression workflows, parameter search, data validation, and ONNX prediction.
[ABOUT THE PROJECT]
This project turns the Python regression workflow into an online AI/ML tool for configuring experiments, running predictions, and explaining the model pipeline.
GNNv3 Online connects a Next.js interface to a FastAPI backend that serves the saved FNN model pipeline. The backend loads the trained artifacts, applies the same scaler and categorical encoder used during training, runs the ONNX model, and returns prediction results in a browser-readable table.
Training is used when you need a new or better model. The website prepares the FNN command and explains the settings, but it does not launch heavy runs from the browser. Long Ax or grid experiments should be run manually on a machine sized for training.
The browser prepares FNN commands and runs prediction. Heavy training is kept outside the website because the VPS is expected to return to 2 vCPUs.
A successful training run produces files that can be reused later: model weights or ONNX export, scaler, encoder, final parameters, and losses.
Grid search tests a fixed list of combinations. Ax search proposes new combinations based on earlier results to find lower validation loss faster.
[PARAMETER INDEX]
Use this index when preparing a run command. Most fields map directly to Python CLI arguments or model training settings.
[CONFIGURE TRAINING]
Select the FNN run mode, feature columns, search strategy, and neural network hyperparameters. The terminal command updates as you work and should be launched manually for training.
python gml.py \ --method FNN \ --mode train \ --use_Ax \ --ax_trials 300 \ --feature_file data/features.tsv \ --scaler PowerTransformer \ --encoding onehot \ --reproduce 5 \ --foldername runs/Trial_1_AX_300 \ --test_size 0.2 \ --n_folds 5 \ --batch_sizes 16,64,256 \ --learning_rates 0.0001,0.001,0.01 \ --n_epochs 500 \ --hidden_layers 1,2,3,5 \ --num_nodes 16,24,32 \ --dropout_rates 0.0,0.1 \ --activation_functions Sigmoid,Tanh,LeakyReLU \ --loss_function SmoothL1Loss \ --optimizers Adam \ --net_shape rectangle
[PROCESS FLOW]
Use the online workbench in two paths: prepare train or test commands for manual execution, and run prediction online when a saved model is ready.
Start with a TSV or CSV file that contains the selected numeric and categorical feature columns. Training also needs the target column.
Choose train, test, or predict, then set the FNN feature names, scaler, encoding, seed, and output folder.
Training creates artifacts, but the website only prepares the command. Large runs should be launched manually from a terminal on suitable hardware.
Prediction loads the saved model pipeline, validates the uploaded file, transforms the data, and appends the PredY output column.
trainPrepares the command for fitting a new FNN model from labeled data and writing model artifacts.
testPrepares the command for evaluating a saved run folder against known target values.
predictUses an existing saved model to generate predictions for new feature rows.
[DATA SCHEMA]
Prediction and training depend on exact column names. Keep the file tab-separated, keep headers stable, and include the selected feature columns.
Use one header row. CSV is accepted for prediction, but TSV remains the workflow default.
Include numeric features, categorical features, and the target column selected in the console.
Include the feature columns only. Target values are optional. The API appends PredY.
Comma-separated parameter lists cannot contain spaces. Column names must match the file header.
[PREDICTION PIPELINE]
Send a feature file to the FastAPI backend. The UI keeps the workflow visible while the model transforms, encodes, and predicts.
> api.loading
> model.none
> features.pending
> search=ax trials=300
> seed=5 folds=5
> training.manual=standby
> prediction.empty
[RUN STATUS]
Prediction results render as a compact table. Training status reflects command preparation only, not a hosted training job.
No prediction output yet. Upload a compatible feature file in step 06.