Compiler in the loop integration (anthropic)#33
Conversation
… support for valid filepaths with nested directory
| ) | ||
|
|
||
|
|
||
| retries, retries_dir, fstub = max_retries, os.path.join(os.curdir, 'retries', 'retries'), 'temp.scenic' |
There was a problem hiding this comment.
checkout using this: https://github.com/KE7/scenicNL/blob/24b1d3597b6b348659a97ca5d6361a5bcde22f2f/src/scenicNL/common.py#L180
it's a bit cleaner
There was a problem hiding this comment.
Yup this looks way better
| verbose: bool, | ||
| max_retries: int | ||
| ) -> str: | ||
| verbose_retry = True |
There was a problem hiding this comment.
I think we can leave it all under the same verbose argument
There was a problem hiding this comment.
Think it might be better to separate out so we can watch it retry as it runs without all the other verbose output it was hard to see what's happening in real time when I tried verbose=true and these runs take 30-60m+
| with open(PromptFiles.AST_FEEDBACK_CLAUDE.value) as f: | ||
| prompt = f.read() | ||
|
|
||
| prompt = prompt.format( |
There was a problem hiding this comment.
I would bubble this up into the caller so the anthropic _ast_prompt function. The reason being is that when we do this for gpt + others, they will use different formatting and so this would get pushed up anyways
There was a problem hiding this comment.
Smart will do this and add gpt and rerequest
…esults but not amazing .. segmenting program into multiple chunks still wip locally
… split reasoning, program combining - add intelligent program reduction/redundancy removal
…tion occasionally has repeat sections -> need debug output
2 participants
max_retriesparameter for claude executionsfuture work