Method 1: Input Directly in the Command Line
The first method is to enter the input variables directly into the command line and is therefore limited to only scalar and text input types. This can be sufficient if you are working with a very simple Notebook. Once in the correct directory, you can use the following command to execute an nTop Notebook in that folder with desired input variables:
Method 2: Input From a JSON File (Recommended)
The recommended method for more complex use is to work with a JSON file containing input values, which supports boolean, integer, scalar, text, file path, vector, point, and enum input types. You can find more information on each specific type under Documentation → Using nTopCL → Input. You can write all your input variables in a single JSON file. The template for this can be automatically generated in the command line using the -t flag with the ntopcl call, which will place one input and one output JSON template file in your directory.


Tip:
Shift + Right-click in your working directory folder and choose “Open Powershell window here” to access the command line without changing the directory.
Running a command with ntop instead of ntopcl opens up the GUI so that you can see the Notebook with the given inputs. Use the first to check if your workflow works properly and as intended.
Adding -s will save the Notebook and overwrite the existing one.
The default verbosity level, which defines how much information you get about the execution as printed messages on the command line screen, is 1 (shows errors and warnings). Add -v2 to your command to change this to level 2 (shows errors, warnings, and run-time information) to see more detailed information. This can be helpful to see which part of the Notebook is causing the issue. To get these messages as a text file, add –logfile LogFile.txt to the command.
Shift + Right-click in your working directory folder and choose “Open Powershell window here” to access the command line without changing the directory.
Running a command with ntop instead of ntopcl opens up the GUI so that you can see the Notebook with the given inputs. Use the first to check if your workflow works properly and as intended.
Adding -s will save the Notebook and overwrite the existing one.
The default verbosity level, which defines how much information you get about the execution as printed messages on the command line screen, is 1 (shows errors and warnings). Add -v2 to your command to change this to level 2 (shows errors, warnings, and run-time information) to see more detailed information. This can be helpful to see which part of the Notebook is causing the issue. To get these messages as a text file, add –logfile LogFile.txt to the command.

