Skip to content

Commit

Permalink
🔖 Release v0.2.0
Browse files Browse the repository at this point in the history
  • Loading branch information
yosh-matsuda committed Oct 8, 2023
1 parent afcf012 commit 2e0741e
Show file tree
Hide file tree
Showing 4 changed files with 7 additions and 4 deletions.
5 changes: 4 additions & 1 deletion .gitignore
Original file line number Diff line number Diff line change
Expand Up @@ -89,7 +89,7 @@ ipython_config.py
# However, in case of collaboration, if having platform-specific dependencies or dependencies
# having no cross-platform support, pipenv may install dependencies that don't work, or not
# install all needed dependencies.
#Pipfile.lock
Pipfile.lock

# PEP 582; used by e.g. github.com/David-OConnor/pyflow
__pypackages__/
Expand Down Expand Up @@ -127,3 +127,6 @@ dmypy.json

# Pyre type checker
.pyre/

# Other
.vscode/
2 changes: 1 addition & 1 deletion README-ja.md
Original file line number Diff line number Diff line change
Expand Up @@ -165,7 +165,7 @@ $ amplify-bench stats preset_20230803_223440.json
| `variables` | `object` | ジョブで使用可能な変数の定義 (Optional) |
| `imports` | `array[string]` | ユーザー定義の問題のファイルパス (Optional) |

`variables` キーに与える変数定義は `jobs` 内で参照することが出来ます。この時、`$` から始まる文字列は変数名として扱われます。例えば次のように全ての問題に共通する設定を与えるときに有用です。
ファイルの中の `$` から始まる文字列は変数名として扱われます。最初に実行時の環境変数によって展開され、その後 `variables` キーに与えた変数定義が `jobs` 内で参照されます。例えば次のように全ての問題に共通する設定を与えるときに有用です。

```yaml
variables:
Expand Down
2 changes: 1 addition & 1 deletion README.md
Original file line number Diff line number Diff line change
Expand Up @@ -165,7 +165,7 @@ A job set file consisted of JSON objects with the following keys. The schema of
| `variables` | `object` | definitions of variables used in `jobs` (Optional) |
| `imports` | `array[string]` | User-defined problem file path (Optional) |

Variable definitions for the `variables` key can be referenced in `jobs`. A string starting with `$` is treated as a variable name. This is useful, for example, to specify a setting that is commonly used in multiple jobs
Strings in the file that begin with `$` are treated as variable names. Variables are first expanded by the environment variables at runtime, then the variable definitions given in the `variables` key are referenced in `jobs`. This is useful, for example, to specify a setting that is commonly used in multiple jobs

```yaml
variables:
Expand Down
2 changes: 1 addition & 1 deletion setup.cfg
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
[metadata]
name = amplify-bench
version = 0.1.3
version = 0.2.0
author = Fixstars Corporation, Fixstars Amplify Corporation
author_email = "Yoshiki Matsuda" <[email protected]>
maintainer = Yoshiki Matsuda, Hiroki Kawahara, Kosuke Suzuki
Expand Down

0 comments on commit 2e0741e

Please sign in to comment.