The explorer picks up almost all information from waku topology/config files --- barring wsl configs and few other; and the wsl config et al. are likely to stay the same across multiple runs.
So it make sense to make the topo/comfig a command line argument so that we could automate the runs end2end --- starting withtopos/config generation to finally analyising the data generated.
The explorer picks up almost all information from waku topology/config files --- barring wsl configs and few other; and the wsl config et al. are likely to stay the same across multiple runs.
So it make sense to make the topo/comfig a command line argument so that we could automate the runs end2end --- starting withtopos/config generation to finally analyising the data generated.