Name changes: GitHub Org, repository, project

[felker]

Minor detail that has been bothering me:

• plasma-python GitHub repository name
• plasma Python module name
• PPPLDeepLearning GitHub Organization name
• "PPPL deep learning disruption prediction package" repository description
• "Fusion Recurrent Neural Network" (FRNN) title of README.md and internal project reference name

are inconsistent and somewhat misleading names for our efforts. While deep RNNs have been the main thrust of the project since its inception in the summer of 2016, using "FRNN" as a shorthand name might be too narrow going forward. Already, the repository contains implementations of a variety of shallow ML methods: random forests, SVMs, single hidden layer perceptrons, and gradient-boosted trees. We have added, or are about to add, deep learning methods that are not based on RNNs, e.g. TCN and Transformers.

Also, not sure if we want to keep PPPL in our GitHub org name, given that we have researchers and team members elsewhere.

Possible changes:

• import plasma ---> import fusionml, import deepfusion
• Repository name plasma-python ---> plasma to be consistent with the folder/module name
• PPPLDeepLearning ---> DeepLearningPPPL, DeepLearningFusion, FusionDeepLearning ?
• Keep "Deep" in our names, since the shallow methods have really only been used for demonstrating that we outperform them?
• FusionML (FML?)
• DeepFusion? "Deep" prefix might be overused at this point... and "Deep Fusion" is an Apple camera technology in the iPhone 11

[felker]

Also, I have started referring to the project as DeepFusionAESP (Aurora Early Science Program) to distinguish it from the first-principles simulation-based project in the A21 ESP with PI C.S. Chang: https://www.alcf.anl.gov/science/projects/high-fidelity-simulation-fusion-reactor-boundary-plasmas

[felker]

I am coming around to "FusionDL". The name of our AESP Project's Unix Group is fusiondl_aesp, and I am now using "FusionDL" in the project tracking documents at ALCF.