I'm attempting to put together a habit in Org Mode that needs to be checked in every 3 out of 4 days (specifically, 3 days on, 1 day off). I'm not entirely certain that this is even possible with the repeating schedule syntax, but wanted to ask and see if anyone has been able to figure this out.
Related
We are trying to build a report in Salesforce for the last 30 days that shows for each day, the amount of cases opened and the amount of cases closed(in total, not how many of the opened were closed). It's just a workload comparison for the support team, so how many cases in vs how many cases out.
Something like
Day 1 . 46 cases opened. 34 cases closed.
Day 2 . 50 cases opened. 52 cases closed.
[...]
Day 30. 36 cases opened. 26 cases closed.
We'd graph that with side by side bars.
We can't get our way around to bucket those two different group by's. As cased closed don't necessarily belog to cases opened that day.
We tried grouping by cases open or closed.
Normal report on Case won't work because you want to count a record twice (once on creation, once on closing... and pray you never reopen cases)
Does it really have to be on single report? You could make a dashboard with 2 report components, that'd be easy, group 1st by CreatedDate, 2nd by ClosedDate.
Or try to run a report on Case History (assuming you do have field history tracking enabled on key fields)
Here's sample "stacked bar" chart of a "Case History" report
(but I have very simple lifecycle, just New -> Closed... if you have more statuses it'll be tricky to filter them out and focus on just closing. Maybe you have a field you set when closing and it's history tracked?)
There's a feature called Case Milestones, check if it could help.
I am having a problem keeping my Gilt Replacement Rate slider continuing to add new animals to my model. I have added in a giltQuarantine delay of 8 weeks just after the source block, which helps to visualize how the gilt replacement rate is working.
Everything is working, initially; however, after several weeks, the giltQuarantine delay drops to
0, and no new gilts enter the herd. The Gilt Replacement Rate adds the desired amount to the model, each week, with no stop time listed.
At around 30 weeks, the number of agents in the giltQuarantine delay begins to
decline and finally becomes 0, while the number of sows in the system is only 167. It should be steadily increasing to 1000 sows.
I cannot see why this is happening, as I should have a consistent supply of gilts
entering the herd each week, which the variable giltReplacement says is happening (see Model running at 54 weeks (screenshot 4)).
I also tried increasing the Gilt Replacement Rate, which worked for several weeks,
but then also declined as the number of sows in the system reached 1024. I want my herd size to remain stable at 1000.
Is there any reason that would be causing this decline in replacement animals?
Probably because you limit the total number of arrivals in enterHerd to breedingHerd. Remove the limit and test it.
Also, you can see current rates and other charactistics of flow chart blocks by clicking on them at runtime. Maybe that helps you pinpoint the issue further.
if nothing works, simplify your setup. It is already fairly complex. If you run into this issue now without knowing what causes it, it shows that you do not follow a good modelling approach (add 1 tiny feature, test everything, repeat) :)
Looking at the attached pic the last commit was 5 days ago, however the first 2 lines show changes 39 mins ago.
https://github.com/popcornmix/xbmc/tree/newclock5
If I click on the change description for the first line then it shows the commit was 3 year ago.
What am I missing here? Am I not understanding the whole commit/date/time thing?
Would appreciate it if someone explained this. I would think the latest commit should then show 39 mins ago?
On git are two types of dates: GIT_AUTHOR_DATE (when you made the original commit) and GIT_COMMITTER_DATE (when patch was applied).
In your example changes was commited 3 years ago but was applied later.
You could read more about author and commiter differences here: https://stackoverflow.com/a/18754896/1349549
Is it possible to specify an event to occur on the 1st weekend day of multiple months every 2 years in a single RRULE? Using February and September as a test case, my first thought was:
FREQ=YEARLY;DTSTART=20140320T070000Z;INTERVAL=2;BYSETPOS=1;BYMONTH=2,9;BYDAY=SA,SU
but BYSETPOS reduces the set down to February only. I thought changing the freq to monthly would do the trick after I posted here, but applying an interval of 2 for every other year messes things up because the interval is applied to a monthly freq instead of a yearly freq.
I made this a new question because I did not include interval in my original question.
I think splitting this into multiple rrules would work, but it would greatly increase the complexity of this area of my app so I was hoping for a single rrule with a yearly freq.
Thanks!
FWIW, and since you mention it as a potential workaround, RFC5545 has removed the ability to have multiple RRULE property in a single VEVENT/VTODO (https://www.rfc-editor.org/rfc/rfc5545#section-3.6.1). It was there in RFC2445.
Then, unless someone finds a very elegant and simple solution, you may be left with something that is so convoluted that most clients will barf on it (don't know how interoperability is important to you).
This leaves you with 2 choices I think:
either use 2 different events (maybe linked with a RELATED-TO property)
or, if you can bound the event to a certain number of instances, represent it as a set of RDATE (or RRULE + RDATE, or RRULE + EXDATE, etc...).
Adding BYSETPOS like this may work as you intend:
FREQ=YEARLY;INTERVAL=2;BYMONTH=2,9;BYDAY=+1SA,+1SU;BYSETPOS=1,3
what you could try is to take advantage of the fact that bysetpos allows you to select within the year the selected instances of your rule, then you could limit the number of instances to the first week of the month (by setting the days of the month to the first 6 ones) to avoid the cases where month have more or less weeks, which then allows you to select the first and third instance in your year.
Which then gives:
DTSTART:20140320T060000Z
FREQ=YEARLY;INTERVAL=2;WKST=MO;BYSETPOS=1,3;BYMONTH=2,9;BYMONTHDAY=1,2,3,4,5,6,7;BYDAY=SA,SU
which will be:
Sat 2014/Sept/6
Sat 2016/Feb/6
Sat 2016/Sep/3
...
Sun 2024/Sep/1
this was verified with dateutil-python and http://jkbr.github.io/,
There are a few complex habits/tasks that I wish orgmode to handle, and I'm not quite sure how to program them:
A habit that has to be done twice a day, between certain hours (E.g. 8-9 and 18-19).
A habit that has to be done over the weekend (Between Thursday-Saturday).
A task that occurs every 6 months, twice a day between certain hours, for a duration of 21 days total.
Can someone help with adding the right SCHEDULE?
Weekend only habit:
SCHEDULED: <2013-12-13 Fri ++1w/2d>
This will cause it to repeat every Friday (regardless of when completed), and will be late if delayed by more than 2 days after the next notification.
Twice a day habit:
This will most likely have to be created as two separate habits, one for the first timeframe and one for the second.
Bi-annual:
Most likely requires two TODO's as well to allow for the two timeframes. I'm not sure if there's any real way of doing so without using complex diary SEXPs which you would have to create every 6 months (or update the SEXP to match the next 6 month span). Org TODOs/Habits don't usually include an 'end-date' when they repeat.