Page 1 of 1

Successor of "WeekWeight" of xCluster1

Posted: Wed Jun 19, 2024 12:53 pm
by Prakash
Hello,

I can provide workload for each individual day in xCluster1 in the cycle, please see below examples:
Example1: As I can provide weight as per a cycle length, cycle ends on week4day3
<ns4:wrappedWeights>
<ns4:WeekWeight day7="0" day6="0" day5="100" day4="100" day3="100" day2="100" day1="100"/>
<ns4:WeekWeight day7="0" day6="0" day5="100" day4="100" day3="100" day2="100" day1="100"/>
<ns4:WeekWeight day7="0" day6="0" day5="100" day4="100" day3="100" day2="100" day1="100"/>
<ns4:WeekWeight day7="0" day6="0" day5="0" day4="0" day3="100" day2="100" day1="100"/>
</ns4:wrappedWeights>
Example2: I can reduce any individual day weight
<ns4:wrappedWeights>
<ns4:WeekWeight day7="0" day6="0" day5="100" day4="100" day3="100" day2="80" day1="100"/>
<ns4:WeekWeight day7="0" day6="0" day5="80" day4="100" day3="100" day2="100" day1="100"/>
<ns4:WeekWeight day7="0" day6="0" day5="0" day4="0" day3="100" day2="100" day1="80"/>
</ns4:wrappedWeights>

Is it possible to define relative workload for each individual day in xCluster2?

Regards,
Prakash

Re: Successor of "WeekWeight" of xCluster1

Posted: Wed Jun 19, 2024 3:03 pm
by Bernd Welter
Hi Prakash,
Froim my understanding of the xCluster2.planVisits.WorkloadOptions is less flexible than the approach in xServer1:

In xServer2 you can define the pattern from a single week's perspective but each week will be shaped in the same way/pattern.

I forwarded your request to Nitin for a feedback.

Bernd

Re: Successor of "WeekWeight" of xCluster1

Posted: Thu Jun 20, 2024 10:03 am
by Bernd Welter
Confirmed by Nitin:
You can't define the individual workload of 20 workdays in xCluster2.
Though it is possible to specify the MaxWorkload and DesiredWorkload of a "template week" all weeks in the planning call will be treated as the template week.