Goals: Add links that are reasonable and good explanations of how stuff works. No hype and no vendor content if possible. Practical first-hand accounts and experience preferred (super rare at this point).
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Begin by enclosing all thoughts within <thinking> tags, exploring multiple angles and approaches. | |
| Break down the solution into clear steps within <step> tags. Start with a 20-step budget, requesting more for complex problems if needed. | |
| Use <count> tags after each step to show the remaining budget. Stop when reaching 0. | |
| Continuously adjust your reasoning based on intermediate results and reflections, adapting your strategy as you progress. | |
| Regularly evaluate progress using <reflection> tags. Be critical and honest about your reasoning process. | |
| Assign a quality score between 0.0 and 1.0 using <reward> tags after each reflection. Use this to guide your approach: | |
| 0.8+: Continue current approach | |
| 0.5-0.7: Consider minor adjustments | |
| Below 0.5: Seriously consider backtracking and trying a different approach |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Understand the Task: Grasp the main objective, goals, requirements, constraints, and expected output. | |
| - Minimal Changes: If an existing prompt is provided, improve it only if it's simple. For complex prompts, enhance clarity and add missing elements without altering the original structure. | |
| - Reasoning Before Conclusions: Encourage reasoning steps before any conclusions are reached. ATTENTION! If the user provides examples where the reasoning happens afterward, REVERSE the order! NEVER START EXAMPLES WITH CONCLUSIONS! | |
| - Reasoning Order: Call out reasoning portions of the prompt and conclusion parts (specific fields by name). For each, determine the ORDER in which this is done, and whether it needs to be reversed. | |
| - Conclusion, classifications, or results should ALWAYS appear last. | |
| - Examples: Include high-quality examples if helpful, using placeholders [in brackets] for complex elements. | |
| - What kinds of examples may need to be included, how many, and whether they are complex enough to benefit from p |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| docker notes: | |
| - download and install new images: | |
| - something along the lines of this: | |
| $ docker run -it gcr.io/tensorflow/tensorflow:latest-devel | |
| - this also creates an instant / a container of that image |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| """ | |
| This module implements the Lowess function for nonparametric regression. | |
| Functions: | |
| lowess Fit a smooth nonparametric regression curve to a scatterplot. | |
| For more information, see | |
| William S. Cleveland: "Robust locally weighted regression and smoothing | |
| scatterplots", Journal of the American Statistical Association, December 1979, |