home.social

#scheduling — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #scheduling, aggregated by home.social.

  1. Is it possible the solution was right there all along??

    I've been on-and-off tweaking the #radar #scheduling #optimization #constraintprogramming #python #software project to include routing

    I kept finding that routing takes longer to figure out than pure packing--no surprise.

    But this was even the case when the constraints put on the routing were extremely minimal.

    This made me wonder how much actual optimization was happening in the NON-routing case. As it turns out, none. If it doesn't have to do any work, it goes fast.

    Sounds pretty obvious, but it's very helpful. Why? See next toot.

  2. Is it possible the solution was right there all along??

    I've been on-and-off tweaking the #radar #scheduling #optimization #constraintprogramming #python #software project to include routing

    I kept finding that routing takes longer to figure out than pure packing--no surprise.

    But this was even the case when the constraints put on the routing were extremely minimal.

    This made me wonder how much actual optimization was happening in the NON-routing case. As it turns out, none. If it doesn't have to do any work, it goes fast.

    Sounds pretty obvious, but it's very helpful. Why? See next toot.

  3. Is it possible the solution was right there all along??

    I've been on-and-off tweaking the project to include routing

    I kept finding that routing takes longer to figure out than pure packing--no surprise.

    But this was even the case when the constraints put on the routing were extremely minimal.

    This made me wonder how much actual optimization was happening in the NON-routing case. As it turns out, none. If it doesn't have to do any work, it goes fast.

    Sounds pretty obvious, but it's very helpful. Why? See next toot.

  4. Is it possible the solution was right there all along??

    I've been on-and-off tweaking the #radar #scheduling #optimization #constraintprogramming #python #software project to include routing

    I kept finding that routing takes longer to figure out than pure packing--no surprise.

    But this was even the case when the constraints put on the routing were extremely minimal.

    This made me wonder how much actual optimization was happening in the NON-routing case. As it turns out, none. If it doesn't have to do any work, it goes fast.

    Sounds pretty obvious, but it's very helpful. Why? See next toot.

  5. Is it possible the solution was right there all along??

    I've been on-and-off tweaking the #radar #scheduling #optimization #constraintprogramming #python #software project to include routing

    I kept finding that routing takes longer to figure out than pure packing--no surprise.

    But this was even the case when the constraints put on the routing were extremely minimal.

    This made me wonder how much actual optimization was happening in the NON-routing case. As it turns out, none. If it doesn't have to do any work, it goes fast.

    Sounds pretty obvious, but it's very helpful. Why? See next toot.

  6. FediSuite

    If you want to take your account seriously, you need consistency. But consistency does not mean sitting at your computer every evening to upload a photo. With FediSuite scheduling, you sit down once, write ten posts for the week and schedule them to the minute in your own timezone. In the background, workers reliably publish your posts on time, even if your instance is overloaded for a moment or a rate limit acts up. After that you can go back to living your life, instead of setting your alarm by your posting plan.

    #FediSuite #Fediverse #Mastodon #Scheduling #SocialMediaTips
    fedisuite.com

  7. FediSuite

    Wenn du deinen Account ernsthaft pflegen willst, brauchst du Regelmäßigkeit. Aber Regelmäßigkeit heißt nicht, dass du jeden Abend pünktlich am Rechner sitzen und ein Foto hochladen musst. Mit dem Scheduling von FediSuite setzt du dich einmal hin, schreibst zehn Beiträge für die Woche und planst sie minutengenau in deiner Zeitzone. Im Hintergrund laufen Worker, die deine Posts pünktlich rausschicken, auch wenn deine Instanz mal überlastet ist oder ein Rate-Limit zickt. Du kannst danach wieder dein Leben leben, statt deinen Wecker nach deinem Posting-Plan zu stellen.

    #FediSuite #Fediverse #Mastodon #Scheduling #SocialMediaTips
    fedisuite.com

  8. In the latest in a series of articles about Debusine, our developers and sysadmins do a deep dive on how they managed to investigate and fix #Debusine workflow performance issues caused by complex interactions between a series of database concurrency and worker communication issues.

    It involved delicate work to avoid system deadlocks, optimizing our workflow orchestration, scheduling fixes, worker refactoring and reducing the high database write volume.

    Read the detailed breakdown at freexian.com/blog/debusine-per

    #freexian #debian #postgresql #scheduling #refactoring

  9. They liked the #constraintprogramming #radar #scheduling talk so much they want me to give it again to our sister group. Whee.

    Meanwhile, when I named it I backronymed it to a name I wanted to use about 10 years ago.

    My boss immediately asked if I also came up with a logo.

    I'm using that question to justify spending the rest of the day designing some options in #inkscape ...

  10. Thank the goddesses for my recent attempts at #music transcription and also for #adhd #rx

    My #constraintprogramming #radar #scheduling talk is in *gulp* two weeks. My rough draft is due FRIDAY.

    5 years ago, I spent a week in front of blank slides, sometimes in tears, unable to even conceive of a method by which I could start.

    Earlier this week, I did at least manage to gather a lot of content slides from other decks but as of this morning it was all just a jumble.

    This morning I took a two-pronged approach

    1. Clear the runway: Do dumb things like checking my inbox, getting a drink and music squared away, etc first. THEN take meds and dive in as they ramp up.

    2. I was having trouble getting started but also specifically having trouble with the start of the slides. But there's no reason the first slide in the deck has to be the first one created.

    For the song I've been working on transcribing, I gave up on "note by note from the beginning" approach. Instead I found spots where it was easy to figure out (single sustained notes, simple melodic progressions, etc). Then I tied those together knowing where the mystery passage had to start and end.

    Why not do the same thing with PowerPoint? I definitely know what I want to say in the "design proposal" section. And I think I know what some future work will be. Start with those parts!

    That only took like 30 minutes. And with that out of the way, it looked a lot more do-able to find some points to make in the "how did we get here" section.

    I now have a (very) rough draft of the talk!

  11. Scene Scheduler: The Ultimate Automation Tool for 24/7 OBS Streaming Scene Scheduler: The Ultimate Automation Tool for 24/7 OBS Streaming Running a professional live stream or a 24/7 broadcast chan...

    #abdul #aziz #ahwan #automation #obs #playout #scene #scheduler #scene #scheduling #scheduler

    Origin | Interest | Match
  12. Selfhosting is nice, and it comes with a price to pay.

    For me ? It's time, and I have plenty to give away, given that's my passion.

    For my SO ? The unbearable noise of rattling disk needles to write on their very precious platters (especially now, thank you AI bullcrap)

    The solution ? A nice cron-based compromise, and I feel like someone could get inspired by this :)

    # Stop qbittorrent - weekday evenings at 17:00 Mon-Fri
    0 17 * * 1-5 cd /opt/services/qbittorrent && docker compose stop

    # Stop qbittorrent - weekends at 8:00 Sat-Sun
    0 8 * * 6,0 cd /opt/services/qbittorrent && docker compose stop

    # Start qbittorrent - every day at 23:00
    0 23 * * * cd /opt/services/qbittorrent && docker compose start

    #selfhosting #selfhosted #homelab #torrent #qbittorrent #harddrive #disk #nas #so #ai #cron #crontab #scheduling #linux #opensource #docker #dockercompose

  13. Selfhosting is nice, and it comes with a price to pay.

    For me ? It's time, and I have plenty to give away, given that's my passion.

    For my SO ? The unbearable noise of rattling disk needles to write on their very precious platters (especially now, thank you AI bullcrap)

    The solution ? A nice cron-based compromise, and I feel like someone could get inspired by this :)

    # Stop qbittorrent - weekday evenings at 17:00 Mon-Fri
    0 17 * * 1-5 cd /opt/services/qbittorrent && docker compose stop

    # Stop qbittorrent - weekends at 8:00 Sat-Sun
    0 8 * * 6,0 cd /opt/services/qbittorrent && docker compose stop

    # Start qbittorrent - every day at 23:00
    0 23 * * * cd /opt/services/qbittorrent && docker compose start

    #selfhosting #selfhosted #homelab #torrent #qbittorrent #harddrive #disk #nas #so #ai #cron #crontab #scheduling #linux #opensource #docker #dockercompose

  14. Selfhosting is nice, and it comes with a price to pay.

    For me ? It's time, and I have plenty to give away, given that's my passion.

    For my SO ? The unbearable noise of rattling disk needles to write on their very precious platters (especially now, thank you AI bullcrap)

    The solution ? A nice cron-based compromise, and I feel like someone could get inspired by this :)

    # Stop qbittorrent - weekday evenings at 17:00 Mon-Fri
    0 17 * * 1-5 cd /opt/services/qbittorrent && docker compose stop

    # Stop qbittorrent - weekends at 8:00 Sat-Sun
    0 8 * * 6,0 cd /opt/services/qbittorrent && docker compose stop

    # Start qbittorrent - every day at 23:00
    0 23 * * * cd /opt/services/qbittorrent && docker compose start

    #selfhosting #selfhosted #homelab #torrent #qbittorrent #harddrive #disk #nas #so #ai #cron #crontab #scheduling #linux #opensource #docker #dockercompose

  15. Selfhosting is nice, and it comes with a price to pay.

    For me ? It's time, and I have plenty to give away, given that's my passion.

    For my SO ? The unbearable noise of rattling disk needles to write on their very precious platters (especially now, thank you AI bullcrap)

    The solution ? A nice cron-based compromise, and I feel like someone could get inspired by this :)

    # Stop qbittorrent - weekday evenings at 17:00 Mon-Fri
    0 17 * * 1-5 cd /opt/services/qbittorrent && docker compose stop

    # Stop qbittorrent - weekends at 8:00 Sat-Sun
    0 8 * * 6,0 cd /opt/services/qbittorrent && docker compose stop

    # Start qbittorrent - every day at 23:00
    0 23 * * * cd /opt/services/qbittorrent && docker compose start

    #selfhosting #selfhosted #homelab #torrent #qbittorrent #harddrive #disk #nas #so #ai #cron #crontab #scheduling #linux #opensource #docker #dockercompose

  16. Selfhosting is nice, and it comes with a price to pay.

    For me ? It's time, and I have plenty to give away, given that's my passion.

    For my SO ? The unbearable noise of rattling disk needles to write on their very precious platters (especially now, thank you AI bullcrap)

    The solution ? A nice cron-based compromise, and I feel like someone could get inspired by this :)

    # Stop qbittorrent - weekday evenings at 17:00 Mon-Fri
    0 17 * * 1-5 cd /opt/services/qbittorrent && docker compose stop

    # Stop qbittorrent - weekends at 8:00 Sat-Sun
    0 8 * * 6,0 cd /opt/services/qbittorrent && docker compose stop

    # Start qbittorrent - every day at 23:00
    0 23 * * * cd /opt/services/qbittorrent && docker compose start

    #selfhosting #selfhosted #homelab #torrent #qbittorrent #harddrive #disk #nas #so #ai #cron #crontab #scheduling #linux #opensource #docker #dockercompose

  17. [Перевод] Планировщик Go

    Эта статья посвящена языку программирования Go 1.24 , работающему на Linux на архитектуре ARM . Она может не охватывать специфические для других операционных систем (ОС) или аппаратных архитектур детали. В этой статье подробно рассматриваются следующие вопросы: Компиляция и среда выполнения Go Примитивный планировщик Улучшение планировщика Модель GMP Начальная загрузка программы Создание горутины Цикл планирования Поиск готовой к выполнения горутины Вытеснение горутин Обработка системных вызовов Сетевой и файловый ввод-вывод Работа netpoll Сборщик мусора Общие функции API среды выполнения Go

    habr.com/ru/companies/timeweb/

    #go #golang #scheduler #scheduling #schedule_loop #планировщик #планирование #цикл_планирования #timeweb_статьи_перевод #goroutine

  18. Or really, I should just rewrite this as a VRP, since it is so close to that anyway and the code I have was just a prototype.

    #constraintprogramming #python #radar #orbit #scheduling #math #computerscience

  19. A true Traveling Salesman Problem on top of the Knapsack Problem takes longer than I want to spend (many minutes vs ~10s) and also does more than I want.

    A forced-greedy TSP (near neighbors are all scored 1, farther nodes are all scored 0) is much faster and closer to what I want but still longer than I want (~2m)

    The solution to a combinatorial problem is not a faster algorithm, it's a smaller problem.

    I need to break the TSP into chunks and solve them separately. The difficult thing is that I need to do this while deliberately remaining unaware of the semantics of the nodes for larger architectural reasons.

    #constraintprogramming #python #radar #orbit #scheduling #math #computerscience

  20. This radar scheduling thing is dominated by a Knapsack Problem with a dash of Traveling Salesman to keep from wearing out hardware/looking dumb.

    I think I have a workable solution to each of these now.

    It took a little while to get the TSP portion to behave usefully. It's funny, because you'd think getting a "feasible" solution would be easier than an optimal one. But in terms of software it's much more difficult--you have to define "feasible".

    The TSP-relevant tasks are the GEO satellite belt. These objects are spread out in a mostly-linear ~150deg azimuthal band that is somewhat clustered. You might have 5 objects within a degree of each other and then nothing for 3 degrees.

    Inside these clumps, I don't care about the path much. But I definitely don't want to zip back and forth between clumps.

    I can't limit to a set time since other jobs may intervene. I can't do it as a percentage since I don't know what percentage these jobs are at ay given time.

    What I ended up doing is basically defining the costs just like I described them above. We have "close' objects (within say 3 degrees) that all have the same cost. Then medium and and large distance.

    For a problem with more time than jobs, I get a reasonable answer in 3s. With more jobs than time, I just set a 10s upper bound and still get a reasonable time.

    I need to integrate this solution with the larger program to really check runtimes with a more realistic set of jobs. But I think I have enough understanding and knobs in place to make this work.

    #constraintprogramming #ortools #scheduling/#routing #optimization #python #software #programming #engineering

  21. I had a #P1e #Ustalav session scheduled for today (20 December) but it was canceled yesterday evening. These things happen around the holidays so it is what it is.

    The campaign is delayed until 03 January now. The party are deep in a ghoul warren. They're facing off with a pair of ghasts. Someone is yelling to be released from a stone sarcophagus in the chamber. They're avoiding a golem in another chamber.

    #Pathfinder1e #PathfinderRPG #PFRPG #TTRPG #ghoul #ghouls #dungeon #Scheduling

  22. #constraintprogramming #ortools #scheduling/#routing #optimization

    I think I may have gotten this working in the toy problem. I can get a list of time-ordered optional intervals AND a circuit in the same order. That will let me put sequential constraints at the circuit level (I hope)

    The key turned out to be to make sure all present intervals were also entered nodes AND that every x->y edge meant that x.time < y.time....and that the reverse is not true!

    It's weird how confused I am by half-reified constraints, given that's *exactly* how programming languages do variable assignment.

    a = b

    makes a take the value b, but not vice versa.