You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: content/learning-paths/servers-and-cloud-computing/gh-runners/background.md
+12-4Lines changed: 12 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -28,17 +28,25 @@ GitHub Actions runs workflow files to automate processes. Workflows run when spe
28
28
29
29
[YAML](https://yaml.org/) defines a workflow.
30
30
31
-
Workflows specify how a job is triggered, the running environment, and the commands to run.
31
+
Workflows specify:
32
32
33
-
The machine running workflows is called a _runner_.
33
+
* How a job is triggered.
34
+
* The running environment.
35
+
* The commands to run.
36
+
37
+
The machine running the workflows is called a _runner_.
34
38
35
39
## Arm-hosted GitHub runners
36
40
37
41
Hosted GitHub runners are provided by GitHub, so you do not need to set up and manage cloud infrastructure. Arm-hosted GitHub runners use the Arm architecture so you can build and test software without the necessity for cross-compiling or instruction emulation.
38
42
39
-
Arm-hosted GitHub runners enable you to optimize your workflows, reduce cost, and improve energy consumption.
43
+
Arm-hosted GitHub runners enable you to:
44
+
45
+
* Optimize your workflows.
46
+
* Reduce cost.
47
+
* Improve energy consumption.
40
48
41
-
Additionally, the Arm-hosted runners are preloaded with essential tools, making it easier for to develop and test your applications.
49
+
Additionally, the Arm-hosted runners are preloaded with essential tools, which makes it easier for to develop and test your applications.
42
50
43
51
Arm-hosted runners are available for Linux and Windows. This Learning Path uses Linux.
Copy file name to clipboardExpand all lines: content/learning-paths/servers-and-cloud-computing/gh-runners/train-test.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -49,7 +49,7 @@ The transformations used when loading data are part of the preprocessing step, w
49
49
50
50
In accordance with common machine learning practices, data is separated into training and testing data to avoid overfitting the neural network.
51
51
52
-
Use this code to load the dataset:
52
+
Here is the code to load the dataset:
53
53
54
54
```python
55
55
transform = transforms.Compose([
@@ -68,7 +68,7 @@ The next step is to define a class for the model, listing the layers used.
68
68
69
69
The model defines the forward pass function used at training time to update the weights. Additionally, the loss function and optimizer for the model are defined.
70
70
71
-
Use this code that defines the model:
71
+
Here is the code that defines the model:
72
72
73
73
```python
74
74
classTrafficSignNet(nn.Module):
@@ -100,7 +100,7 @@ A training loop performs the actual training.
100
100
101
101
The number of epochs is arbitrarily set to 10 for this example. When the training is finished, the model weights are saved to a `.pth` file.
102
102
103
-
Use this code for the training loop:
103
+
Here is the code for the training loop:
104
104
105
105
```python
106
106
num_epochs =10
@@ -143,7 +143,7 @@ Testing is done by loading the model that was saved after training and preparing
143
143
144
144
As in training, transformations are used to load the test data from the GTSRB dataset.
145
145
146
-
Use this code to load the model and the test data:
146
+
Here is the code to load the model and the test data:
147
147
148
148
```python
149
149
model_path = args.model if args.model else'./models/traffic_sign_net.pth'
0 commit comments