Re: [Fawkes Trac] #384: gazsim: still standing simulaiton clock at start

[Fawkes Trac]

#384: gazsim: still standing simulaiton clock at start
+---
  Reporter:  fzwilling  |  Owner:  fzwilling
  Type:  defect | Status:  closed
  Priority:  major  |  Milestone:
 Component:  Carologistics  |Version:
Resolution:  fixed  |   Keywords:
Git Branch: |
+---
Changes (by fzwilling):

 * status:  accepted => closed
 * resolution:   => fixed


Comment:

 Solved by https://github.com/robocup-logistics/gazebo-
 rcll/commit/8ca234402c825805fb45fdd26e10f62ec3706adc

 Thanks Tim

-- 
Ticket URL: 
Fawkes Trac 
Fawkes Robotics Software Framework
___
fawkes-trac mailing list
fawkes-trac@lists.kbsg.rwth-aachen.de
https://lists.kbsg.rwth-aachen.de/listinfo/fawkes-trac

Re: [Fawkes Trac] #384: gazsim: still standing simulaiton clock at start

[Fawkes Trac]

#384: gazsim: still standing simulaiton clock at start
+---
  Reporter:  fzwilling  |  Owner:  fzwilling
  Type:  defect | Status:  closed
  Priority:  major  |  Milestone:
 Component:  Carologistics  |Version:
Resolution:  fixed  |   Keywords:
Git Branch: |
+---

Comment (by tim):

 That seems to have fixed the initialization problem described in
 [wiki:Carologistics/Gazsim-Setup-2015 Gazebo setup] with error messages of
 the form "!ColliThread: !LaserInterface writer has been inactive for too
 long (1.094230 > 0.50)".

 It didn't matter anymore when I actually started the game, i.e. whether I
 waited for Fawkes startup to complete or started the game already before.

 Awesome, thanks a lot! Maybe we can now even speed-up simulation startup.
 What about adding flags to the refbox for setting the team name and auto-
 starting the game right away? Would that be a welcome addition?

-- 
Ticket URL: 
Fawkes Trac 
Fawkes Robotics Software Framework
___
fawkes-trac mailing list
fawkes-trac@lists.kbsg.rwth-aachen.de
https://lists.kbsg.rwth-aachen.de/listinfo/fawkes-trac

Re: [Fawkes Trac] #384: gazsim: still standing simulaiton clock at start

[Fawkes Trac]

#384: gazsim: still standing simulaiton clock at start
+---
  Reporter:  fzwilling  |  Owner:  fzwilling
  Type:  defect | Status:  accepted
  Priority:  major  |  Milestone:
 Component:  Carologistics  |Version:
Resolution: |   Keywords:
Git Branch: |
+---
Changes (by fzwilling):

 * status:  reopened => accepted


Comment:

 Hm, ok. Did you also compile the changes in gazebo-rcll/plugins? When this
 happens, do you have messages published on the gazsim/time-sync/ topic?

-- 
Ticket URL: 
Fawkes Trac 
Fawkes Robotics Software Framework
___
fawkes-trac mailing list
fawkes-trac@lists.kbsg.rwth-aachen.de
https://lists.kbsg.rwth-aachen.de/listinfo/fawkes-trac

Re: [Fawkes Trac] #384: gazsim: still standing simulaiton clock at start

[Fawkes Trac]

#384: gazsim: still standing simulaiton clock at start
+---
  Reporter:  fzwilling  |  Owner:  fzwilling
  Type:  defect | Status:  accepted
  Priority:  major  |  Milestone:
 Component:  Carologistics  |Version:
Resolution: |   Keywords:
Git Branch: |
+---

Comment (by tim):

 Yes, I did compile. I have merged the time-sync and gripper fix branches.

 The bug seems to occur much less often. I wasn't able to reproduce the
 error a second time in 20-30 starts (with 1 and 3 robots). It might
 indicate that you need a very specific timing in triggering this error
 now.

 Let's make the speedup a new ticket.

-- 
Ticket URL: 
Fawkes Trac 
Fawkes Robotics Software Framework
___
fawkes-trac mailing list
fawkes-trac@lists.kbsg.rwth-aachen.de
https://lists.kbsg.rwth-aachen.de/listinfo/fawkes-trac

Re: [Fawkes Trac] #384: gazsim: still standing simulaiton clock at start

[Fawkes Trac]

#384: gazsim: still standing simulaiton clock at start
+---
  Reporter:  fzwilling  |  Owner:  fzwilling
  Type:  defect | Status:  closed
  Priority:  major  |  Milestone:
 Component:  Carologistics  |Version:
Resolution:  fixed  |   Keywords:
Git Branch: |
+---
Changes (by fzwilling):

 * status:  new => closed
 * resolution:   => fixed


Comment:

 Solved in the fzwilling/time-sync-fix branch in gazebo-rcll.
 The problem was an uninitialized time variable which caused that no time
 messages were sent with an unlucky initialization.

-- 
Ticket URL: 
Fawkes Trac 
Fawkes Robotics Software Framework
___
fawkes-trac mailing list
fawkes-trac@lists.kbsg.rwth-aachen.de
https://lists.kbsg.rwth-aachen.de/listinfo/fawkes-trac

Re: [Fawkes Trac] #384: gazsim: still standing simulaiton clock at start

[Fawkes Trac]

#384: gazsim: still standing simulaiton clock at start
+---
  Reporter:  fzwilling  |  Owner:  fzwilling
  Type:  defect | Status:  reopened
  Priority:  major  |  Milestone:
 Component:  Carologistics  |Version:
Resolution: |   Keywords:
Git Branch: |
+---
Changes (by tim):

 * status:  closed => reopened
 * resolution:  fixed =>


Comment:

 Damn, didn't fix it. Had it again after a few more tries :-/

 The symptom also stays the same that the refbox time-sync stops once this
 happens.

-- 
Ticket URL: 
Fawkes Trac 
Fawkes Robotics Software Framework
___
fawkes-trac mailing list
fawkes-trac@lists.kbsg.rwth-aachen.de
https://lists.kbsg.rwth-aachen.de/listinfo/fawkes-trac

Re: [Fawkes Trac] #384: gazsim: still standing simulaiton clock at start

[Fawkes Trac]

#384: gazsim: still standing simulaiton clock at start
+---
  Reporter:  fzwilling  |  Owner:  fzwilling
  Type:  defect | Status:  accepted
  Priority:  major  |  Milestone:
 Component:  Carologistics  |Version:
Resolution: |   Keywords:
Git Branch: |
+---

Comment (by fzwilling):

 Adding flags to the refbox, which automatically set the Team and start the
 Setup phase would be cool. But I am a bit careful with decreasing the
 waiting times at simulation start because this could mess up the start for
 slower computers. Some kind of indicator when the simulation init finished
 would be useful but I don't know what we could use there.

-- 
Ticket URL: 
Fawkes Trac 
Fawkes Robotics Software Framework
___
fawkes-trac mailing list
fawkes-trac@lists.kbsg.rwth-aachen.de
https://lists.kbsg.rwth-aachen.de/listinfo/fawkes-trac