Skip to content

Commit 9ac93f7

Browse files
Update README.md
1 parent 981aaa6 commit 9ac93f7

File tree

1 file changed

+24
-11
lines changed

1 file changed

+24
-11
lines changed

README.md

Lines changed: 24 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -136,19 +136,32 @@ It is a convention to write data designating modalities with @ sign taken by Top
136136
#### CubeCreator helps to perform a grid search over initial model parameters. How can I do it with modalities?
137137

138138
Modality search space can be defined using standart library logic like:
139-
```,k
140-
name: 'class_ids',
141-
values: {
142-
'@text': [1, 2, 3],
143-
'@ngrams': [4, 5, 6],
144-
},
145139
```
146-
However for the case of modalities a couple of slightly more convenient methods are availiable:
140+
class_ids_cube = CubeCreator(
141+
num_iter=5,
142+
parameters: [
143+
name: 'class_ids',
144+
values: {
145+
'@text': [1, 2, 3],
146+
'@ngrams': [4, 5, 6],
147+
},
148+
]
149+
reg_search='grid',
150+
verbose=True
151+
)
147152
148153
```
149-
[{'name': 'class_ids@text', 'values': [1, 2, 3]},
150-
{'name': 'class_ids@ngrams', 'values': [4, 5, 6]}]
151-
{'class_ids@text': [1, 2, 3],
152-
'class_ids@ngrams': [4, 5, 6]}
154+
However for the case of modalities a couple of slightly more convenient methods are availiable:
153155

154156
```
157+
parameters : [
158+
{'name': 'class_ids@text', 'values': [1, 2, 3]},
159+
{'name': 'class_ids@ngrams', 'values': [4, 5, 6]}
160+
]
161+
parameters:[
162+
{
163+
'class_ids@text': [1, 2, 3],
164+
'class_ids@ngrams': [4, 5, 6]
165+
}
166+
]
167+
```

0 commit comments

Comments
 (0)