Create an interactive artifact of an analog clock face that keeps time properly.
https://claude.ai/public/artifacts/75daae76-3621-4c47-a684-d...
131–140 of 404 posts
Create an interactive artifact of an analog clock face that keeps time properly.
https://claude.ai/public/artifacts/75daae76-3621-4c47-a684-d...
https://slate.com/human-interest/2016/07/martin-baas-giant-r...
Since the first (good) image generation models became available, I've been trying to get them to generate an image of a clock with 13 instead of the usual 12 hour divisions. I have not been successful. Usually they will just replace the "12" with a "13" and/or mess up the clock face in some other way. I'd be interested if anyone else is successful. Share how you did it!
I’m very curious about the monthly bill for such a creative project, surely some of these are pre rendered?
Napkin math: 9 AIs × 43,200 minutes = 388,800 requests/month 388,800 requests × 200 tokens = 77,760,000 tokens/month ≈ 78M tokens Cost varies from 10 cents to $1 per 1M tokens. Using the mid-price, the cost is around $50/month. --- Hopefully, the OP has this endpoint protected - https://clocks.brianmoore.com/api/clocks?time=11:19AM
Since the first (good) image generation models became available, I've been trying to get them to generate an image of a clock with 13 instead of the usual 12 hour divisions. I have not been successful. Usually they will just replace the "12" with a "13" and/or mess up the clock face in some other way. I'd be interested if anyone else is successful. Share how you did it!
LLMs are terrible for out-of-distribution (OOD) tasks. You should use chain of thought suppression and give constaints explictly. My prompt to Grok: --- Follow these rules exactly: - There are 13 hours, labeled 1–13. - There are 13 ticks. - The center of each number is at angle: index * (360/13) - Do not infer anything else. - Do not apply knowledge of normal clocks. Use the following variables: HOUR_COUNT = 13 ANGLE…