@@ -135,6 +135,20 @@ If everything is specified in the config file, there are still few must-have opt
...
@@ -135,6 +135,20 @@ If everything is specified in the config file, there are still few must-have opt
--save-strategy-as-json-file='timing.json'
--save-strategy-as-json-file='timing.json'
-u
-u
```
```
- Same observation as above, but all modification parameters are given in the configuration file called `timing-id520.yaml` and this time we are not saving strategy into the output JSON file:
- FRB observation, the test pulsar should be specified in the `specs.json` file. Name of the FRB is different in the specification, so we use `--target` option to give the new FRB name, but it can't be resolved by `astropy`, so we use `--no-target-resolve` option to prevent resolving the given name, and also providing the coordinates with `--ra` and `--dec` options. Also, we use `now` value for the `--tstart` option meaning that observation will start after the delay of 5 min from the current moment. This delay can be also controlled with `--delay` option which is 300 sec, by default.
- FRB observation, the test pulsar should be specified in the `specs.json` file. Name of the FRB is different in the specification, so we use `--target` option to give the new FRB name, but it can't be resolved by `astropy`, so we use `--no-target-resolve` option to prevent resolving the given name, and also providing the coordinates with `--ra` and `--dec` options. Also, we use `now` value for the `--tstart` option meaning that observation will start after the delay of 5 min from the current moment. This delay can be also controlled with `--delay` option which is 300 sec, by default.