Skip to content

Commit 656b4dc

Browse files
committed
Adding peer review feedback
1 parent 7c40f27 commit 656b4dc

File tree

1 file changed

+9
-4
lines changed

1 file changed

+9
-4
lines changed

modules/rhoai-demo-app.adoc

+9-4
Original file line numberDiff line numberDiff line change
@@ -57,7 +57,7 @@ https://github.com/redhat-developer-demos/openshift-ai.git
5757

5858
. Click the *Clone* button.
5959

60-
. After fetching the github repository, the project will appear in the directory section on the left side of the notebook.
60+
. After fetching the github repository, the project appears in the directory section on the left side of the notebook.
6161

6262
. Expand the */openshift-ai/1_First-app/* directory.
6363

@@ -67,9 +67,9 @@ You will be presented with the view of a Jupyter Notebook.
6767

6868
## Running code in a Jupyter notebook
6969

70-
In the previous section, you imported and opened the notebook. To run the code within the notebook, you start by clicking the *Run* icon located at the top of the interface. This action initiates the execution of the code in the currently selected cell.
70+
In the previous section, you imported and opened the notebook. To run the code within the notebook, click the *Run* icon located at the top of the interface.
7171

72-
After you click *Run*, you will notice that the notebook automatically moves to the next cell. This is part of the design of Jupyter Notebooks, where scripts or code snippets are divided into multiple cells. Each cell can be run independently, allowing you to test specific sections of code in isolation. This structure greatly aids in both developing complex code incrementally and debugging it more effectively, as you can pinpoint errors and test solutions cell by cell.
72+
After clicking *Run*, the notebook automatically moves to the next cell. This is part of the design of Jupyter Notebooks, where scripts or code snippets are divided into multiple cells. Each cell can be run independently, allowing you to test specific sections of code in isolation. This structure greatly aids in both developing complex code incrementally and debugging it more effectively, as you can pinpoint errors and test solutions cell by cell.
7373

7474
After executing a cell, you can immediately see the output just below it. This immediate feedback loop is invaluable for iterative testing and refining of code.
7575

@@ -155,7 +155,7 @@ image::rhoai/predict-step4.png[Interactive Real-Time Data Streaming and Visualiz
155155

156156
.. Running the cell in Step 5, produces an output of two images, one of a cat and one of a dog, with their respective predictions labeled as "Cat" and "Dog".
157157

158-
.. Once the code in the cell is executed in Step 6, a predict button will appear as shown in screenshot below. The interactive session displays images with their predicted labels in real-time as the user clicks the *Predict* button. This dynamic interaction helps in understanding how well the model performs across a random set of images and provides insights into potential improvements for model training.
158+
.. Once the code in the cell is executed in Step 6, a predict button appears as shown in screenshot below. The interactive session displays images with their predicted labels in real-time as the user clicks the *Predict* button. This dynamic interaction helps in understanding how well the model performs across a random set of images and provides insights into potential improvements for model training.
159159
+
160160
image::rhoai/predict.png[Interactive Real-Time Image Prediction with Widgets]
161161

@@ -178,3 +178,8 @@ For example make these modifications in your notebook or another Python environm
178178
# Adjust the number of epochs and steps per epoch
179179
model.fit(train_generator, steps_per_epoch=100, epochs=10)
180180
----
181+
182+
[role="_additional-resources"]
183+
.Additional resources
184+
185+
* link:https://developers.redhat.com/learn/openshift-ai[Red Hat OpenShift AI learning]

0 commit comments

Comments
 (0)