screen recording utilizes OBS Studio
waste of context
14 Matching Annotations
- Last 7 days
-
-
-
e believe that annotation error is not all bad, aslong as we can identify and utilize them
self-correction should be based on strategically included flows, not repeated-pattern human error
-
The complete action space and its parameters are listed in Table 1.
bad action space
-
computer as the observation for the agent
expecting to represent a high-complexity complete Turing machine as the vision space seems weak (s_i -> 1024x768x3). exaggerated info loss. images cound only retain the relevant tile for vision encoder
-
convert compute state si into modelobservation
vague
-
computer state
WHAT?
-
wait
requires sec arg with action-tailored estimate
-
text
string only makes sense in OOP, the OS deals with stdio
-
‘success’ or ‘failure’
could contain max_steps and/or timeout
-
aT : P (ai|I, s0, a0, . . . , si)
tautology
-
Axtree
needs clarification
-
moveTo
why? just need drag(x0,y0,x1,u1)
-
hscroll
why hscroll if dy in scroll
-
middleClick
why not button=button
-