Skip to content

Commit 3421a2d

Browse files
committed
updating readme with FAQ
1 parent 00d0180 commit 3421a2d

File tree

1 file changed

+70
-0
lines changed

1 file changed

+70
-0
lines changed

lib/allora/README.md

Lines changed: 70 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -157,4 +157,74 @@ We will use AWS Cloud9 to execute the subsequent commands. Follow the instructio
157157
```bash
158158
aws iam delete-instance-profile --instance-profile-name Cloud9-Developer-Access
159159
aws iam delete-role --role-name Cloud9-Developer-Access
160+
```
161+
162+
### FAQ
163+
164+
1. How to check the logs from the EC2 user-data script?
165+
166+
Please enter the [AWS Management Console - EC2 Instances](https://us-east-2.console.aws.amazon.com/ec2/home?region=us-east-2#Instances:instanceState=running), choose the correct region, copy the instance ID you need to query.
167+
168+
```bash
169+
pwd
170+
# Make sure you are in aws-blockchain-node-runners/lib/allora
171+
172+
export INSTANCE_ID="i-**************"
173+
echo "INSTANCE_ID=" $INSTANCE_ID
174+
aws ssm start-session --target $INSTANCE_ID --region $AWS_REGION
175+
sudo cat /var/log/cloud-init-output.log
176+
```
177+
2. How to check the worker node connectivity to the Allora Network?
178+
179+
Please enter the [AWS Management Console - EC2 Instances](https://us-east-2.console.aws.amazon.com/ec2/home?region=us-east-2#Instances:instanceState=running), choose the correct region, copy the instance ID you need to query.
180+
181+
```bash
182+
pwd
183+
# Make sure you are in aws-blockchain-node-runners/lib/allora
184+
185+
export INSTANCE_ID="i-**************"
186+
echo "INSTANCE_ID=" $INSTANCE_ID
187+
aws ssm start-session --target $INSTANCE_ID --region $AWS_REGION
188+
```
189+
190+
You should be able to query Topic 1 on the Allora Network and see similar output below
191+
```bash
192+
$ allorad q emissions topic 1 --node https://allora-rpc.testnet-1.testnet.allora.network
193+
effective_revenue: "0"
194+
topic:
195+
allow_negative: true
196+
alpha_regret: "0.1"
197+
creator: allo1lzf3xp0zqg4239mrswd0cclsgt3y8fl7l84hxu
198+
default_arg: ETH
199+
epoch_last_ended: "183177"
200+
epoch_length: "120"
201+
ground_truth_lag: "120"
202+
id: "1"
203+
inference_logic: bafybeifqs2c7ghellof657rygvrh6ht73scto3oznw4i747sqk3ihy7s5m
204+
inference_method: allora-inference-function.wasm
205+
loss_logic: bafybeid7mmrv5qr4w5un6c64a6kt2y4vce2vylsmfvnjt7z2wodngknway
206+
loss_method: loss-calculation-eth.wasm
207+
metadata: ETH 10min Prediction
208+
p_norm: "3"
209+
tolerance: "0.001"
210+
weight: "0"
211+
```
212+
3. How to check the Allora worker containers are running?
213+
214+
Please enter the [AWS Management Console - EC2 Instances](https://us-east-2.console.aws.amazon.com/ec2/home?region=us-east-2#Instances:instanceState=running), choose the correct region, copy the instance ID you need to query.
215+
216+
```bash
217+
pwd
218+
# Make sure you are in aws-blockchain-node-runners/lib/allora
219+
220+
export INSTANCE_ID="i-**************"
221+
echo "INSTANCE_ID=" $INSTANCE_ID
222+
aws ssm start-session --target $INSTANCE_ID --region $AWS_REGION
223+
```
224+
225+
```bash
226+
[ec2-user@ip-192-168-0-224 ~]$ docker ps -a
227+
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
228+
b10c12c51f32 worker-worker "allora-node allora-…" 18 hours ago Exited (2) 18 hours ago worker
229+
05273577ce7a alloranetwork/allora-inference-base-head:latest "allora-node allora-…" 18 hours ago Exited (2) 18 hours ago head
160230
```

0 commit comments

Comments
 (0)