Chauffeuring a Crashed Robot from a Disk
Debasish Pattanayak, H. Ramesh, and Partha Sarathi Mandal

TL;DR
This paper addresses fault-tolerant evacuation algorithms for two robots on a disk with a hidden exit, focusing on minimizing worst-case evacuation time despite crash faults and varying travel speeds.
Contribution
It introduces algorithms for evacuating two robots with one possible crash fault, including a lower bound and analysis for different travel time ratios.
Findings
Algorithms tolerate one crash fault during evacuation.
A lower bound for evacuation time is established.
Performance varies with travel time ratio and crash timing.
Abstract
Evacuation of robots from a disk has attained a lot of attention recently. We visit the problem from the perspective of fault-tolerance. We consider two robots trying to evacuate from a disk via a single hidden exit on the perimeter of the disk. The robots communicate wirelessly. The robots are susceptible to crash faults after which they stop moving and communicating. We design the algorithms for tolerating one fault. The objective is to minimize the worst-case time required to evacuate both the robots from the disk. When the non-faulty robot chauffeurs the crashed robot, it takes amount of time to travel unit distance. With this, we also provide a lower bound for the evacuation time. Further, we evaluate the worst-case of the algorithms for different values of and the crash time.
Peer Reviews
No public reviews on file for this paper yet. If you reviewed it on a platform where reviews are public (OpenReview, ICLR, NeurIPS, ICML), you can paste yours below so the community can read it here.
Videos
No videos yet. Explain this paper in a talk, walkthrough, or lecture? Add one.
11institutetext: Indian Institute of Technology Guwahati, India
11email: {p.debasish,ramesh_h,psm}@iitg.ac.in
Chauffeuring a Crashed Robot from a Disk
Debasish Pattanayak
H. Ramesh
and Partha Sarathi Mandal
Abstract
Evacuation of robots from a disk has attained a lot of attention recently. We visit the problem from the perspective of fault-tolerance. We consider two robots trying to evacuate from a disk via a single hidden exit on the perimeter of the disk. The robots communicate wirelessly. The robots are susceptible to crash faults after which they stop moving and communicating. We design the algorithms for tolerating one fault. The objective is to minimize the worst-case time required to evacuate both the robots from the disk. When the non-faulty robot chauffeurs the crashed robot, it takes amount of time to travel unit distance. With this, we also provide a lower bound for the evacuation time. Further, we evaluate the worst-case of the algorithms for different values of and the crash time.
1 Introduction
Searching has always been a classical problem and by extension, the search of a hidden object in a domain has piqued the interest. In particular, a variant of search problem introduced by Czyzowicz et al. [5] as the evacuation problem, which tries to minimize the time required for the last searcher to reach the target. The searchers, in this case, are mobile robots which can move around in the domain. The domain considered can be a convex shape like a disk, a circle or a triangle [2, 3, 4], while the target is hidden on the boundary. Another variant of the problem considers the domain as lines and rays [1] with faulty robots [11, 12]. The objective here is to minimize the competitive ratio between the time required for the robot to reach the exit and the distance from the exit.
The recent literature has focused on the aspect of collective-collaborative search. Czyzowicz et al. [5] introduced two robots trying to search for an exit located on the perimeter of a unit disk. A robot can locate the exit only when it is at the exit. There are two models of communication between the robots, namely, wireless and face-to-face. In face-to-face, the robots can exchange messages if they are collocated at the same point at the same time. They showed that the evacuation time for two robots in the wireless model was , which was optimal. In the same paper, they achieved an upper bound of and lower bound for two robots in the face-to-face model. In a subsequent paper, Czyzowicz et al. [10] improved the upper and lower bounds to and , respectively. Later Brandt et al. [2], further improved the upper bound to .
Further Czyzowicz et al. [7] study priority evacuation of a particular robot from the disk, namely the Queen, while other servant robots search for the exit. This paper sets the upper and lower bounds for evacuation for one, two and three servants. Another paper by Czyzowicz et al. [8] presents the bounds for .
Another aspect of this evacuation problem deals with fault-tolerance. The two types of faults considered are crash fault and byzantine fault. The type of crash fault considered in [6, 11] does not detect the target when it passes through or does not communicate when it finds the target. The robots with byzantine faults in [6, 9] even lie about the position of the target. Czyzowicz et al. [6] focused on minimizing the evacuation time for the latest non-faulty robot. They achieved a lower bound of and upper bound for three robots out of which at most one is susceptible to crash fault with wireless communication. We initiate the study on a type of crash fault, where the robot stops moving and sending messages altogether (unlike [6]). Instead of abandoning the crashed robot, our objective is to chauffeur it to the exit in the least time. As a natural outcome, we consider the robot which chauffeurs the crashed robots incurs an extra cost. The chauffeur carrying the crashed robot travels at a fraction of its original speed.
Our Contributions:
In this paper, we consider a variant of crash fault where the affected robot stops moving and communicating after it has crashed. We address the problem of evacuation for two robots out of which at most one can be faulty. We propose three evacuation algorithms in the wireless communication model where the non-faulty robot chauffeurs the crashed robot.
- •
We present a lower bound for evacuation time.
- •
We rigorously analyze our algorithms to provide the worst-case evacuation time corresponding to the crash time at which a robot becomes faulty.
- •
We compare the performance of the algorithms given particular values of the crash time () and the chauffeuring cost ().
2 Model and Preliminaries
We consider the evacuation of two robots from a unit disk, i.e., a disk with radius one. Let and be the robots. The disk contains an exit located on its perimeter. Both robots have to evacuate the disk. Initially, the robots are situated at the center of the disk and start moving at the same time towards the perimeter of the disk. A robot can find an exit only when it reaches the position of that exit.
We follow a convention that denotes the arc along the perimeter on the disk starting at and ending at moving in the counter-clockwise direction. Accordingly, is the complement of the arc . We abuse the notation to denote the length of the arc and to denote the length of the chord corresponding to the arc . Note that, the length of a chord corresponding to an arc of length is .
Both robots travel at a uniform speed of one unit distance per unit time. We consider that the robots are susceptible to crash faults. A robot which has been crashed stops moving and communicating thenceforth. At most a single robot is faulty. Suppose, has crashed, can still chauffeur to the exit. A non-faulty robot chauffeuring the crashed robot travels at a speed times the original speed. In other words, it takes time to travel unit distance, where .
The robots can communicate by sending messages wirelessly. The communication is reliable. For analytical purposes, we ignore the message propagation delay. The robots communicate frequently with each other. Without loss of generality, let be the time after which crashes. So is the distance travelled by the robot after reaching the perimeter at a speed of one unit distance per unit of time before it crashes at time . We also follow a convention that is the distance of the exit in the counter-clockwise direction starting from the point where has reached the perimeter. So, as shown in Fig. 2. We assume that is the origin and is the positive -axis.
Evacuation Problem (2,1)-crash fault:
The objective is to minimize the time required by the latest robot to evacuate from the unit disk via an exit located on the perimeter of the disk starting from the center of the disk, where both robots travel at uniform speed of one unit distance per unit time and at most one robot is faulty out of the two. Chauffeuring the faulty robot increases the time for movement by a factor for the non-faulty robot.
3 Lower Bounds for Wireless Communication
The lower bound for wireless communication model without faults is [5]. Hence, the lower bound is applicable to the crash fault model if the crash time . We have the following theorems if the robot crashes before evacuation.
Theorem 3.1
The lower bound for evacuation with crash fault for crash time is .
Proof
Consider the simple case where the robot crashes at the center of the disk immediately after it is activated. As the adversary can always place the exit at a position which is still unexplored, it requires at least time to search for the exit on the perimeter by the non-faulty robot. Additionally, is the minimum time required for the faulty robot to be carried to the exit from the center. Since the non-faulty robot can also travel to the perimeter while carrying the faulty robot, it does not need additional time to reach the perimeter. Then the worst-case time for evacuation for the faulty robot is always greater than . Similarly, if , we have the lower bound for evacuation at
[TABLE]
where the robots travel together for a distance , and the non-faulty robot chauffeurs the faulty robot rest of the distance to the perimeter.
Lemma 1 (Lemma 5 from [5])
Consider a perimeter of a disk whose subset of total length has not been explored for some and . Then there exist two unexplored boundary points between which the distance along the perimeter is at least .
Intuitively, the proof follows from this argument. If is the unexplored part of the perimeter and it is a continuous arc, then the endpoints of the arc are separated by at least the same distance along the perimeter. Otherwise, if the unexplored part is separated into multiple arcs, then the distance between two farthest endpoints of the two arcs are at least separated by a distance which is greater than the unexplored part . A detailed proof is available in [5].
Theorem 3.2
The lower bounds for evacuation with crash fault for crash time are
- •
* for *
- •
* for *
- •
* for *
Proof
If , then we claim that the robots evacuate before any of them fails. By the time , two robots can explore at most on the perimeter. The unexplored part is . According to Lemma 1, there exist two unexplored points such that the smallest arc between them is at least . If a robot is at one of the unexplored points, then the adversary can place the exit at the other unexplored point and the exit is found. The robot, which does not find the exit, can receive a message and travel to the exit along a straight line through the disk. The evacuation time in that case is over all possible values of . This results in a worst-case at , which is . Since, the crash time is more than the worst-case evacuation time, both robots evacuate before the fault occurs and the lower bound for evacuation is .
If , the robot can fail at any moment before the evacuation occurs. For this part of the proof, consider that the exit is found at time by . In the worst-case travels a distance from its own position towards the exit in a straight line. The distance between the two robots is , so the robots can meet at the midpoint of that chord at time . If fails before the midpoint, then has to travel extra distance to chauffeur . Otherwise, they meet at the midpoint and travel together. In that case, if fails, chauffeurs the remaining distance. The following two cases present the evacuation time if the robot fails before or after the midpoint.
Fault before the midpoint ():
has to travel extra distance of to reach from midpoint and chauffeur it for a distance . The evacuation time is .
Fault after the midpoint():
and have already met and are travelling together. The distance needs to chauffeur is . The chauffeuring distance adds the cost by a factor of since the robots were already travelling towards the same destination. The evacuation time is .
Theorem 3.3
The lower bound for evacuation with crash fault for crash time is \max_{w-1\leq t\leq 2\pi-2(w-1)}\big{(}1+t+2(\alpha+1)\cos(t/4)\big{)} where is the time for finding the exit and is the part of the perimeter explored by the crashed robot.
Proof
The lower bounds we describe are irrespective of the points where the robots hit the perimeter starting from the center of the disk. There can be two cases depending on the relation between crash time and the time an exit is found by one of the robots. Case 1: If a robot crashes after the exit is found, i.e., , then the robot not near the exit position is already travelling towards the exit. So, the worst-case time of evacuation would happen if and only if the robot crashes at the moment the exit is found, i.e., . The worst-case distance from the crash position to exit is the diameter. If the robot covers part of the perimeter around the antipodal position () of the crashed robot position (), then the maximum distance between the crashed position and exit is at most as shown in Fig. 1. The worst-case evacuation time is .
Case 2: Suppose the exit is found at time . By the time the faulty robot crashes at , it has covered at most on the perimeter. Consider two points and as shown in Fig. 1 which are at a distance from the crashed position for some small value of . If the adversary places the exit in the , then it would take at least to explore the arc. The distance from any point on the arc is greater than . The time required for evacuation is at least
[TABLE]
For a value of , this still holds. Then the time for evacuation is
[TABLE]
The above expression holds as a lower bound since the robot which finds the exit at time has to be at the exit and we show the linear distance between exit and crash position is at least . As the robot has already crashed, the optimal path is to go to the crashed robot and pick up along the chord.
Remark 1
For , expression 2 results in evacuation time for .
4 Upper Bound for Wireless Communication
The upper bound for evacuation in the wireless communication model is . This is the worst-case evacuation time of the algorithm proposed by Czyzowicz et al. [5]. In this paper, we also present evacuation strategies which determine the upper bound with chauffeuring. First, we present a simple strategy to put a ceiling on the upper bound. Next, we present two algorithms which provide us a tighter upper bound with respect to the crash time.
4.1 Trivial Upper Bound (Algorithm (MoveTogether))
Since at most one robot can be faulty, a trivial strategy is to just move both robots along the same path on the perimeter of the disk. Even if one of the robots becomes faulty, the other robot can chauffeur it and continue its search along the perimeter until it finds the exit. Then both the robots can evacuate via the exit as shown in Fig. 2.
The time required for this evacuation algorithm is at most in the case where both robots are free of fault until the evacuation, where the time required to reach the perimeter is 1 and to search the perimeter is . If a robot becomes faulty after time from the activation, then the execution of the algorithm requires the following time
(3)
where denotes the trivial upper bound with respect to the crash time and .
4.2 Evacuation Algorithm (MoveOpposite)
We start with a base algorithm which works with robots without faults. Both robots move together to an arbitrary point on the perimeter starting from the center and then move in opposite directions, i.e., clockwise and counter-clockwise as shown in Fig. 3. Once a robot finds the exit, it sends a message to the other robot. On receiving the message, the other robot finds the position of the sender which is also the position of the exit by time of arrival of the message, knowledge of other robot’s path and speed. Then it proceeds for evacuation along the straight line joining its current position and the exit.
As one of the robots can be faulty, it cannot communicate after it crashes. To determine the position of the crashed robot, we assume that the robots communicate with each other constantly in very small intervals. If a robot crashes and then it fails to send a message, which determines the position of the crashed robot. There can be two simple strategies in the aftermath of the crash. The non-faulty robot can carry the faulty robot and search together or the non-faulty robot searches for the exit without carrying the faulty robot. If both robots are travelling together, then they evacuate the moment the exit is found. Otherwise, the robot which finds the exit sends a message and both robots meet on the chord joining them. When the fault occurs, the non-faulty robot meets the faulty robot, then it chauffeurs the faulty robot to the exit. It increases the time required by a factor of . We describe the two strategies, where the exit is found after a robot has crashed in Section 4.2.1 and 4.2.2. An intermediate strategy, where the robot does not immediately pick up the robot after crash and searches for some distance on the perimeter, performs worse than the two aforementioned strategies. Please refer the appendix for more details.
4.2.1 SearchTogetherAfterCrash
Two robots start together at the same time from the center as shown in Fig. 3. Suppose the robot crashes at after a time at a distance along the arc from the point , where the robots reach the perimeter of the disk, i.e., . is at when crashes at . moves to along the chord and continues the search starting from on . Suppose the exit is located at and according to the convention, is the closest point in the clockwise direction from where a robot has reached the perimeter, so . By extension, . The time taken for the evacuation is , i.e.,
[TABLE]
The worst-case position of exit for which the evacuation time is maximum when is at an infinitesimally small distance from in the clockwise direction, i.e., . Then the worst-case evacuation time for this strategy is
[TABLE]
The worst-case evacuation time would be the maximum time over all possible values of . For , the critical point is obtained at , i.e.,
[TABLE]
Since, , the critical point is a local maximum. The worst-case evacuation time is obtained at . As the value of ranges between and , the maximum value of for which the critical point acts as the maximum is , i.e., .
Remark 2
For , the SearchTogetherAfterCrash strategy has the same worst-case evacuation time as algorithm .
4.2.2 SearchAloneAfterCrash
Similarly, the robots and start at the center of the disk at the same time and move towards the perimeter. crashes at . But continues to move along its own path until it finds the exit at . Let be the distance along the arc to the exit from the point where the robots have hit the perimeter, i.e., . Then the distance from the crashed position of at to the exit at is as shown in Fig. 4. The time required for to reach the exit is . The time for evacuation would be,
[TABLE]
Suppose the crash position of robot is fixed. Then the worst-case location of exit would be a critical point of , i.e., .
[TABLE]
Note that, , so is a monotonically decreasing function with respect to . Failure of a robot is not dependent on the position of the exit. So the variables and are independent. Hence, the worst-case evacuation time is obtained at . The worst-case evacuation time is . Now let us determine the value of for which the worst-case evacuation time of algorithm exceeds the worst-case of SearchAloneAfterCrash strategy. The worst-case evacuation time of algorithm from Equation 3 is for . So,
[TABLE]
The solution to Equation 9 is the value of for which the worst-case of SearchAloneAfterCrash strategy coincides with algorithm . The corresponding is 1.30346. Hence, for values of , algorithm has a better worst-case evacuation time compared to SearchAloneAfterCrash strategy.
For the case where a robot becomes faulty before it reaches the perimeter, the non-faulty robot searches for the exit and then it picks up the faulty robot. Let be the position of faulty robot and be the position of the exit.
[TABLE]
Remark 3
If the exit is found before a robot crashes, then the worst-case would occur when it crashes on the perimeter.
Since and start moving towards each other as soon as the exit is found and if finds the exit, then moves towards the exit moving along the line joining them. Hence, if crashes on the perimeter, that would result in the worst-case. Conversely, if finds the exit, it moves towards along the line joining them. would move at most to the midpoint of the line joining them. If becomes faulty at the midpoint of the line, then the evacuation time is less compared to when it failed at the perimeter.
For , both strategies perform worse compared to the trivial algorithm at . Both the strategies can be combined into one since the path of the robots remain the same until one of them crashes. Note that, the evacuation time has a local maximum at for SearchTogetherAfterCrash strategy for , while it monotonically decreases for SearchAloneAfterCrash strategy. Since the evacuation time for is the same for both strategies at , the SearchAloneAfterCrash strategy performs better for all value of .
Now, let us determine the value of for which both strategies perform the same, i.e., . We have the following.
[TABLE]
For , we have the solution for from Equation 11. Let be a solution to Equation 11. If , then the other robot follows SearchTogetherAfterCrash, otherwise it follows SearchAloneAfterCrash strategy. For , the SearchAloneAfterCrash strategy performs better than the algorithm , where the worst-case of the SearchTogetherAfterCrash strategy is always greater than or equal to worst-case of algorithm . Hence, combination of the strategies will not yield a better result for .
4.3 Evacuation Algorithm (MoveSameDirection)
In this section, we describe an algorithm where the robots start from the center of the disk at the same time at an angle with each other, where . After reaching the perimeter, both robots start travelling in the counter-clockwise direction. Without loss of generality, let us assume that crashes at time . We measure the angle in the counter-clockwise direction from the faulty robot .
The base strategy divides the perimeter into two arcs of length and . Each robot explores its own arc after reaching the perimeter from the center. For , would finish exploring its part of the arc. Then it will try to meet the other robot. Let us determine a meeting point (ref. Fig. 5(a)) such that . The length, , of can be determined from the following equation.
[TABLE]
We can determine that the points and coincide for . So would move along for (ref. Fig. 5(a)) and along for (ref. Fig. 5(b)). For , a similar path is followed by .
Now, we describe the action a robot takes if it finds an exit. On finding the exit, a robot messages the other robot. Then both robots start moving towards each other along the line joining them and meet at the midpoint (ref. Fig. 5(c) and (d)). Thenceforth both robots move towards the exit. If both robots are already travelling together, they evacuate via the exit (ref. Fig. 5(e)).
When crashes, it stops moving and stays there. Once has completely explored its own arc on the perimeter, then it moves to the position of and they explore the remaining part of the perimeter together if the exit is not found by that time. Since we assume that is the robot which crashes, we claim that if the exit is found by , then it would never result in the worst-case. The claim can be proved by the fact that if crashes, then the evacuation time would be higher. By symmetricity, there exists a situation where crashes corresponding to an exit found by . So, in the following cases, we only explain the scenarios with finding the exit.
Case 1:
If crashes before the exit is found, then explores its own arc to search for the exit.
- •
If exit lies on ’s arc, then picks up from its crash position. The evacuation time is
[TABLE]
where is the distance from the exit to the crash position and is the distance of the exit from the point where reaches the boundary in the counter-clockwise direction. The coordinates of exit position are . The coordinates of the crash position are given by
[TABLE]
where if . Equation 13 has two values of , such that . The critical point may be a local maximum according to second derivative test. Hence the value of which provides the worst-case evacuation time for a given value of may be a critical point or a boundary point of domain of depending on the value of and .
- •
If exit lies on ’s arc, picks up by travelling along a line joining the crash position and current position of and they explore the remaining part together. The evacuation time is
[TABLE]
where is the distance between crash position and position of at time determined similar to the previous case. In this case, the worst-case position of exit is just before the point where hits the perimeter, i.e., for an .
Case 2:
If crashes after the exit is found, then is already moving towards along the line joining them. The evacuation time is
[TABLE]
where the distance between the crash position and position of at time determined similar to Case 1.
5 Comparison between Algorithms
We numerically evaluate the behavior of proposed algorithms. The worst-case evacuation time with respect to the crash time for specific values of is evaluated. are chosen as values of since at these points behavior of the algorithms change according to the analysis in Section 4. The crash time is varied in , because it takes amount of time for a single non-faulty robot to evacuate from the disk. The evacuation times are evaluated at discrete values of with a gap of . For each value of , all possible worst-case positions of the exit are considered for Algorithms , and .
As shown in Fig. 6, Algorithm performs better than for . For , Algorithm is optimal. Observe that, performs better compared to for . The lower bound is dominated by for for crash time . Also, for , the smallest worst-case evacuation time is found for discrete values of with a step size of . We also evaluate the lower bound at the same values of . Fig. 7 shows the corresponding value of for which the worst-case evacuation time is obtained for and the four values of . Observe that, for , performs the best for algorithm when crash time .
6 Conclusion
In this paper, we have introduced and analyzed evacuation algorithms for two robots out of which one can be faulty. Along with this, we also provide a lower bound for the evacuation time. For chauffeuring cost the worst-case evacuation time is equal to the lower bound for crash time . This makes Algorithm optimal. As the value of crash time increases beyond , the gap between the lower bound and evacuation time of is very small for all values of . For , the lower bound is very close to the minimum evacuation time of and , which says that the lower bound is tight. But the same does not happen for larger values of , where the lower bound is not very close.
This paper revisits the evacuation problem from a fault-tolerance aspect with one of the classical crash fault scenarios. The model can be further extended for generalized crash fault model with robots out of which are faulty. Further, it is interesting to design algorithms which can tighten the bounds presented in this paper.
Appendix 0.A Comparison between strategies in Wireless Communication
Two robots start together from the center at the same time as shown in Fig. 8. Let be the robot that crashes at . is at the point at the same time. travels up to the point at a distance along the arc before it decides to pick up .
Then the worst-case evacuation time appears if the exit is at a small distance from in the unexplored part. The time for evacuation is . The function is is monotonically increasing with respect to up to and then monotonically decreases. So if , then it is better to maximize . And if , then it is better to have .
Remark 4
Going for meet-up immediately when the other robot fails is better compared to going for the crashed robot later if the exit is not found.
The reference list from the paper itself. Each links out to its DOI / PubMed record.
- 1[1] S. Brandt, K. Foerster, B. Richner, and R. Wattenhofer. Wireless evacuation on m rays with k searchers. In SIROCCO, Porquerolles, France , pages 140–157, 2017.
- 2[2] S. Brandt, F. Laufenberg, Y. Lv, D. Stolz, and R. Wattenhofer. Collaboration without communication: Evacuating two robots from a disk. In CIAC, Athens , pages 104–115, 2017.
- 3[3] H. Chuangpishit, K. Georgiou, and P. Sharma. Average case - worst case tradeoffs for evacuating 2 robots from the disk in the face-to-face model. In Algorithms for Sensor Systems - 14th International Symposium on Algorithms and Experiments for Wireless Sensor Networks, ALGOSENSORS 2018, Helsinki, Finland, August 23-24, 2018, Revised Selected Papers , pages 62–82, 2018.
- 4[4] H. Chuangpishit, S. Mehrabi, L. Narayanan, and J. Opatrny. Evacuating an equilateral triangle in the face-to-face model. In OPODIS, Lisbon, Portugal , pages 11:1–11:16, 2017.
- 5[5] J. Czyzowicz, L. Gasieniec, T. Gorry, E. Kranakis, R. Martin, and D. Pajak. Evacuating robots via unknown exit in a disk. In DISC, USA, October 12-15, 2014. , pages 122–136, 2014.
- 6[6] J. Czyzowicz, K. Georgiou, M. Godon, E. Kranakis, D. Krizanc, W. Rytter, and M. Wlodarczyk. Evacuation from a disc in the presence of a faulty robot. In SIROCCO, Porquerolles, France , pages 158–173, 2017.
- 7[7] J. Czyzowicz, K. Georgiou, R. Killick, E. Kranakis, D. Krizanc, L. Narayanan, J. Opatrny, and S. M. Shende. God save the queen. In 9th International Conference on Fun with Algorithms, FUN 2018, June 13-15, 2018, La Maddalena, Italy , pages 16:1–16:20, 2018.
- 8[8] J. Czyzowicz, K. Georgiou, R. Killick, E. Kranakis, D. Krizanc, L. Narayanan, J. Opatrny, and S. M. Shende. Priority evacuation from a disk using mobile robots - (extended abstract). In Structural Information and Communication Complexity - 25th International Colloquium, SIROCCO 2018, Ma’ale Ha Hamisha, Israel, June 18-21, 2018, Revised Selected Papers , pages 392–407, 2018.
