domino logo
Tech Ecosystem
Get started with Python
Step 0: Orient yourself to DominoStep 1: Create a projectStep 2: Configure your projectStep 3: Start a workspaceStep 4: Get your files and dataStep 5: Develop your modelStep 6: Clean up WorkspacesStep 7: Deploy your model
Get started with R
Step 0: Orient yourself to Domino (R Tutorial)Step 1: Create a projectStep 2: Configure your projectStep 3: Start a workspaceStep 4: Get your files and dataStep 5: Develop your modelStep 6: Clean up WorkspacesStep 7: Deploy your model
Get Started with MATLAB
Step 1: Orient yourself to DominoStep 2: Create a Domino ProjectStep 3: Configure Your Domino ProjectStep 4: Start a MATLAB WorkspaceStep 5: Fetch and Save Your DataStep 6: Develop Your ModelStep 7: Clean Up Your Workspace
Step 8: Deploy Your Model
Scheduled JobsLaunchers
Step 9: Working with Domino Datasets
Domino Reference
Notifications
On-Demand Open MPI
Configure MPI PrerequisitesFile Sync MPI ClustersValidate MPI VersionWork with your ClusterManage Dependencies
Projects
Projects Overview
Revert Projects and Files
Revert a ProjectRevert a File
Projects PortfolioReference ProjectsProject Goals in Domino 4+
Git Integration
Git Repositories in DominoGit-based Projects with CodeSyncWorking from a Commit ID in Git
Jira Integration in DominoUpload Files to Domino using your BrowserFork and Merge ProjectsSearchSharing and CollaborationCommentsDomino Service FilesystemCompare File RevisionsArchive a Project
Advanced Project Settings
Project DependenciesProject TagsRename a ProjectSet up your Project to Ignore FilesUpload files larger than 550MBExporting Files as a Python or R PackageTransfer Project Ownership
Domino Runs
JobsDiagnostic Statistics with dominostats.jsonNotificationsResultsRun Comparison
Advanced Options for Domino Runs
Run StatesDomino Environment VariablesEnvironment Variables for Secure Credential StorageUse Apache Airflow with Domino
Scheduled Jobs
Domino Workspaces
WorkspacesUse Git in Your WorkspaceRecreate A Workspace From A Previous CommitUse Visual Studio Code in Domino WorkspacesPersist RStudio PreferencesAccess Multiple Hosted Applications in one Workspace Session
Spark on Domino
On-Demand Spark
On-Demand Spark OverviewValidated Spark VersionConfigure PrerequisitesWork with your ClusterManage DependenciesWork with Data
External Hadoop and Spark
Hadoop and Spark OverviewConnect to a Cloudera CDH5 cluster from DominoConnect to a Hortonworks cluster from DominoConnect to a MapR cluster from DominoConnect to an Amazon EMR cluster from DominoRun Local Spark on a Domino ExecutorUse PySpark in Jupyter WorkspacesKerberos Authentication
On-Demand Ray
On-Demand Ray OverviewValidated Ray VersionConfigure PrerequisitesWork with your ClusterManage DependenciesWork with Data
On-Demand Dask
On-Demand Dask OverviewValidated Dask VersionConfigure PrerequisitesWork with Your ClusterManage DependenciesWork with Data
Customize the Domino Software Environment
Environment ManagementDomino Standard EnvironmentsInstall Packages and DependenciesAdd Workspace IDEsAdding Jupyter Kernels
Use Custom Images as a Compute Environment
Pre-requisites for Automatic Custom Image CompatibilityModify the Default Workspace ToolsCreate a Domino Image with an NGC ContainerCreate a Domino Environment with a Pre-Built ImageManually Modify Images for Domino Compatibility
Partner Environments for Domino
Use MATLAB as a WorkspaceUse Stata as a WorkspaceUse SAS as a Workspace
Advanced Options for Domino Software Environment
Publish in Domino with Custom ImagesInstall Custom Packages in Domino with Git IntegrationAdd Custom DNS Servers to Your Domino EnvironmentConfigure a Compute Environment to User Private Cran/Conda/PyPi MirrorsUse TensorBoard in Jupyter Workspaces
Publish your Work
Publish a Model API
Model Publishing OverviewModel Invocation SettingsModel Access and CollaborationModel Deployment ConfigurationPromote Projects to ProductionExport Model ImageExport to NVIDIA Fleet Command
Publish a Web Application
App Publishing OverviewGet Started with DashGet Started with ShinyGet Started with FlaskContent Security Policies for Web Apps
Advanced Web Application Settings in Domino
App Scaling and PerformanceHost HTML Pages from DominoHow to Get the Domino Username of an App Viewer
Launchers
Launchers OverviewAdvanced Launcher Editor
Assets Portfolio Overview
Model Monitoring and Remediation
Monitor WorkflowsData Drift and Quality Monitoring
Set up Monitoring for Model APIs
Set up Prediction CaptureSet up Drift DetectionSet up Model Quality MonitoringSet up NotificationsSet Scheduled ChecksSet up Cohort Analysis
Set up Model Monitor
Connect a Data SourceRegister a ModelSet up Drift DetectionSet up Model Quality MonitoringSet up Cohort AnalysisSet up NotificationsSet Scheduled ChecksUnregister a Model
Use Monitoring
Access the Monitor DashboardAnalyze Data DriftAnalyze Model QualityExclude Features from Scheduled Checks
Remediation
Cohort Analysis
Review the Cohort Analysis
Remediate a Model API
Monitor Settings
API TokenHealth DashboardNotification ChannelsTest Defaults
Monitoring Config JSON
Supported Binning Methods
Model Monitoring APIsTroubleshoot the Model Monitor
Connect to your Data
Data in Domino
Datasets OverviewProject FilesDatasets Best Practices
Connect to Data Sources
External Data VolumesDomino Data Sources
Connect to External Data
Connect Domino to DataRobotConnect to Amazon S3 from DominoConnect to Azure Data Lake StorageConnect to BigQuery from DominoConnect to Generic S3 from DominoConnect to Google Cloud StorageConnect to IBM DB2 from DominoConnect to IBM Netezza from DominoConnect to Impala from DominoConnect to MSSQL from DominoConnect to MySQL from DominoConnect to Okera from DominoConnect to Oracle Database from DominoConnect to PostgreSQL from DominoConnect to Redshift from DominoConnect to Snowflake from DominoConnect to Teradata from Domino
Work with Data Best Practices
Work with Big Data in DominoWork with Lots of FilesMove Data Over a Network
Advanced User Configuration Settings
User API KeysDomino TokenOrganizations Overview
Use the Domino Command Line Interface (CLI)
Install the Domino Command Line (CLI)Domino CLI ReferenceDownload Files with the CLIForce-Restore a Local ProjectMove a Project Between Domino DeploymentsUse the Domino CLI Behind a Proxy
Browser Support
Get Help with Domino
Additional ResourcesGet Domino VersionContact Domino Technical SupportSupport Bundles
domino logo
About Domino
Domino Data LabKnowledge BaseData Science BlogTraining
User Guide
>
Get started with R
>
Step 5: Develop your model

Step 5: Develop your model

When you are developing your model, you want to be able to quickly execute code, see outputs, and make iterative improvements. Domino enables this with Workspaces. Step 3 covered starting a Workspace and explored Workspace options like VSCode, RStudio, and Jupyter.

In this section, we will use Rstudio to load, explore, and transform some data. After the data has been prepared, we will train a model.

Step 5.1: Load and explore the dataset

  1. If you have not done so, complete Step 4 to download the dataset. You should see data.csv in /mnt in files pane. If not, return to Step 4 to download the dataset.

    rstudio_files

  2. Use the New menu to create a R script and save is as power.R.

    rstudio_first_df

  3. Enter these lines to import some packages:

    library(tidyverse)
    library(lubridate)
  4. Create a list of the columns according to information on the column headers at https://www.bmreports.com/bmrs/?q=generation/fueltype/current.

    col_names <-  c('HDF', 'date', 'half_hour_increment',
         'CCGT', 'OIL', 'COAL', 'NUCLEAR',
         'WIND', 'PS', 'NPSHYD', 'OCGT',
         'OTHER', 'INTFR', 'INTIRL', 'INTNED',
         'INTEW', 'BIOMASS', 'INTEM')
  5. Read the file you downloaded into a dataframe and set the column names, then display the data:

    #Load the data into a data frame
    df <- read.csv('data.csv',header = FALSE,col.names = col_names,stringsAsFactors = FALSE)
    
    #remove the first and last row
    df <- df[-1,]
    df <- df[-nrow(df),]
    
    #Preview the data
    View(df)
  6. Execute the script by selecting Code > Source. This opens the content of the df data frame in a new tab:

    rstudio first df

    We can see that this is a time series dataset. Each row is a successive half hour increment during the day that details the amount of energy generated by fuel type. Time is specified by the date and half_hour_increment columns.

  7. Tidy that data so that variables are in columns, observations are in rows, and values are in cells. Switch back to the power.R code tab and add the following:

    df_tidy <- df %>% gather('CCGT', 'OIL', 'COAL', 'NUCLEAR',
                    'WIND', 'PS', 'NPSHYD', 'OCGT',
                    'OTHER', 'INTFR', 'INTIRL', 'INTNED',
                    'INTEW', 'BIOMASS', 'INTEM', key="fuel", value="megawatt" )
  8. Create a new column datetime that represents the starting datetime of the measured increment. For example, a 20190930 date and 2 half hour increment means that the time period specified is September 19, 2019 from 12:30am to 12:59am.

    df_tidy <- df_tidy %>% mutate(datetime=as.POSIXct(as.Date(date, "%Y%m%d"))+minutes(30*(half_hour_increment-1)))
  9. Visualize the data to see how each fuel type is used during the day by plotting the data.

    #plot the graph
    p <- ggplot(data=df_tidy, aes(x=datetime, y=megawatt, group=fuel)) +
      geom_line(aes(color=fuel))
    print(p)

    Execute the script again by selecting Code > Source. This will update the Plot tab:

    fuel types graph cell r

    The CCGT column representing "combined-cycle gas turbines" seems to be the most interesting. It generates a lot of energy and is very volatile.

    We will concentrate on this column and try to predict the power generation from this fuel source.

Step 5.2: Train a model

Data scientists have access to many libraries and packages that help with model development. Some of the most common for R are randomForest, caret, and nnet. These packages are already installed in the Domino Standard Environment, the default environment. However, there may be times that you want to experiment with a package that is new and not installed in the environment.

We will build a model with the Facebook Prophet package, which is not installed into the default environment. You will see that you can quickly get started with new packages and algorithms just as fast as they are released into the open source community.

  1. In your R console, install Facebook Prophet. This might take >5 minutes to install. If it fails, make sure that you’ve selected a hardware tier with >2gb of ram:

    # Install specific version of the prerequisite RcppParallel package as its latest version 5.0.2 fails to install
    install.packages('https://cran.r-project.org/src/contrib/Archive/RcppParallel/RcppParallel_5.0.1.tar.gz', repos=NULL, type="source")
    # Now install latest version of Facebook Prophet
    install.packages('prophet')
  2. For Facebook Prophet, the time series data needs to be in a DataFrame with 2 columns named ds and y. Let’s rename the columns and filter to just to fuel type "CCGT":

    df_CCGT <- df_tidy %>% filter(fuel=="CCGT") %>% select(datetime,megawatt)
    
    names(df_CCGT) <- c("ds","y")
  3. Split the dataset into train and test sets:

    split_index <- round(nrow(df_CCGT)*.8)
    df_CCGT_train <- df_CCGT[1:split_index,]
    df_CCGT_test <- df_CCGT[(split_index+1):nrow(df_CCGT),]
  4. Import Facebook Prophet and fit a model:

    library(prophet)
    m <- prophet(df_CCGT_train)
  5. Make a DataFrame to hold prediction and predict future values of CCGT power generation:

    predict_ln <- round(nrow(df_CCGT_test)/2)
    future <- make_future_dataframe(m, periods = predict_ln,freq = 1800 )
    forecast <- predict(m, future)
  6. Plot the fitted line with the training and test data:

    p <- dyplot.prophet(m, forecast)
    print(p)
  7. Save the code.

Step 5.3: Export the model

Trained models are meant to be used. There is no reason to re-train the model each time you use the model. Export or serialize the model to a file to load and reuse the model later. In R, you can commonly use the saveRDS command to create RDS files.

  1. Export the trained model as an rds file for later use:

    saveRDS(m, file = "model.rds")

We will use the serialized model in Step 7 when we create an API from the model.

Domino Data LabKnowledge BaseData Science BlogTraining
Copyright © 2022 Domino Data Lab. All rights reserved.