Local vs. remote mode for auto-discovery#69
Conversation
|
|
||
| 1. Ask about their research goal. | ||
| 2. Inspect their datasets (`head -5 file.csv`, check JSON structure, etc.) to understand columns, units, and size. | ||
| 3. Draft the configuration in whatever shape the local CLI expects (check `asta-autodiscovery --help` for the exact format — flags, config file, or stdin). |
There was a problem hiding this comment.
does this not use the metadata.json shape expected by remote autodiscovery? would it be useful to keep input and output artifacts usable in either context?
regan-huff
left a comment
regan-huff
left a comment
There was a problem hiding this comment.
either via the hosted service (
asta autodiscovery) or via the local CLI (asta-autodiscovery)
This naming and comment are confusing to me. Both are available in CLI, right? and someone runningasta --helpwould see them both? Could we make it easier to understand which is which?
Is running locally actually free? Doesn't the user need to supply api keys for LLM usage?
8917ee7 to
1ec531f
Compare
|
Cleaned up the instructions further. Clarified need for user credentials for local mode. The local CLI actually constructs a |
1ec531f to
175a14b
Compare
175a14b to
2b15274
Compare
2 participants
Add workflow for running AD both locally and on the deployed Asta service