YoanSallami
commited on
Commit
·
fa1e750
1
Parent(s):
b08d128
Fix useful typo
Browse files
code_examples/1_basics/2_first_programs.py
CHANGED
@@ -96,7 +96,7 @@ async def _(AnswerWithThinking, Query, synalinks):
|
|
96 |
inputs=_x0,
|
97 |
outputs=_x1,
|
98 |
name="chain_of_thought",
|
99 |
-
description="
|
100 |
)
|
101 |
return language_model, program
|
102 |
|
@@ -104,7 +104,7 @@ async def _(AnswerWithThinking, Query, synalinks):
|
|
104 |
@app.cell
|
105 |
def _(program):
|
106 |
# You can print a summary of your program in a table format
|
107 |
-
# which is really
|
108 |
|
109 |
program.summary()
|
110 |
return
|
@@ -143,7 +143,7 @@ def _(mo):
|
|
143 |
def _(AnswerWithThinking, language_model, synalinks):
|
144 |
|
145 |
class ChainOfThought(synalinks.Program):
|
146 |
-
"""
|
147 |
|
148 |
The first line of the docstring is provided as description for the program
|
149 |
if not provided in the `super().__init__()`. In a similar way the name is
|
@@ -220,7 +220,7 @@ def _(ChainOfThought, Query, language_model, synalinks):
|
|
220 |
ChainOfThought(language_model=language_model),
|
221 |
],
|
222 |
name="chain_of_thought",
|
223 |
-
description="
|
224 |
)
|
225 |
program_2.summary()
|
226 |
return (program_2,)
|
|
|
96 |
inputs=_x0,
|
97 |
outputs=_x1,
|
98 |
name="chain_of_thought",
|
99 |
+
description="Useful to answer in a step by step manner.",
|
100 |
)
|
101 |
return language_model, program
|
102 |
|
|
|
104 |
@app.cell
|
105 |
def _(program):
|
106 |
# You can print a summary of your program in a table format
|
107 |
+
# which is really useful to have a quick overview of your application
|
108 |
|
109 |
program.summary()
|
110 |
return
|
|
|
143 |
def _(AnswerWithThinking, language_model, synalinks):
|
144 |
|
145 |
class ChainOfThought(synalinks.Program):
|
146 |
+
"""Useful to answer in a step by step manner.
|
147 |
|
148 |
The first line of the docstring is provided as description for the program
|
149 |
if not provided in the `super().__init__()`. In a similar way the name is
|
|
|
220 |
ChainOfThought(language_model=language_model),
|
221 |
],
|
222 |
name="chain_of_thought",
|
223 |
+
description="Useful to answer in a step by step manner.",
|
224 |
)
|
225 |
program_2.summary()
|
226 |
return (program_2,)
|
code_examples/1_basics/5_rewards_metrics_and_optimizers.py
CHANGED
@@ -134,7 +134,7 @@ async def _(synalinks):
|
|
134 |
inputs=_x0,
|
135 |
outputs=_x1,
|
136 |
name="chain_of_thought",
|
137 |
-
description="
|
138 |
)
|
139 |
|
140 |
program.compile(
|
|
|
134 |
inputs=_x0,
|
135 |
outputs=_x1,
|
136 |
name="chain_of_thought",
|
137 |
+
description="Useful to answer in a step by step manner.",
|
138 |
)
|
139 |
|
140 |
program.compile(
|
code_examples/1_basics/6_training_programs.py
CHANGED
@@ -85,7 +85,7 @@ async def _(gsm8k_input_data_model, gsm8k_output_data_model, synalinks):
|
|
85 |
inputs=_x0,
|
86 |
outputs=_x1,
|
87 |
name="chain_of_thought",
|
88 |
-
description="
|
89 |
)
|
90 |
return language_model, program
|
91 |
|
@@ -135,7 +135,7 @@ def _(mo):
|
|
135 |
larger batch will take longer to process and still result in only one update.
|
136 |
- **Epochs**: A epochs is an arbitrarly cutoff, generally defined as "one pass
|
137 |
over the entire dataset", used to separate training into distinct phases,
|
138 |
-
which is
|
139 |
`validation_split` or `validation_data` with the `fit` method of Synalinks
|
140 |
programs, evaluation will be run at the end of every epoch.
|
141 |
"""
|
|
|
85 |
inputs=_x0,
|
86 |
outputs=_x1,
|
87 |
name="chain_of_thought",
|
88 |
+
description="Useful to answer in a step by step manner.",
|
89 |
)
|
90 |
return language_model, program
|
91 |
|
|
|
135 |
larger batch will take longer to process and still result in only one update.
|
136 |
- **Epochs**: A epochs is an arbitrarly cutoff, generally defined as "one pass
|
137 |
over the entire dataset", used to separate training into distinct phases,
|
138 |
+
which is useful for logging and periodic evaluation. When using
|
139 |
`validation_split` or `validation_data` with the `fit` method of Synalinks
|
140 |
programs, evaluation will be run at the end of every epoch.
|
141 |
"""
|
code_examples/2_advanced/1_implementing_custom_modules_and_programs_via_subclassing.py
CHANGED
@@ -244,7 +244,7 @@ def _(mo):
|
|
244 |
|
245 |
To add a variable to the module, you have to use the `add_variables` function,
|
246 |
this function can only be used in the `__init__()` or in the `build()` function.
|
247 |
-
The build function is
|
248 |
based on the actual inputs, that is not known at this stage, remember the module can
|
249 |
accept any inputs.
|
250 |
|
|
|
244 |
|
245 |
To add a variable to the module, you have to use the `add_variables` function,
|
246 |
this function can only be used in the `__init__()` or in the `build()` function.
|
247 |
+
The build function is useful to create variables, or initialize your module/program
|
248 |
based on the actual inputs, that is not known at this stage, remember the module can
|
249 |
accept any inputs.
|
250 |
|