You can subscribe to this list here.
| 2008 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(3) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2009 |
Jan
|
Feb
|
Mar
(2) |
Apr
(6) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2010 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(1) |
Oct
|
Nov
|
Dec
|
| 2012 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(2) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2013 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(3) |
Sep
|
Oct
|
Nov
|
Dec
|
| 2014 |
Jan
(6) |
Feb
(28) |
Mar
(27) |
Apr
(28) |
May
|
Jun
(6) |
Jul
(3) |
Aug
|
Sep
|
Oct
(2) |
Nov
|
Dec
|
| 2015 |
Jan
(2) |
Feb
|
Mar
|
Apr
|
May
|
Jun
(2) |
Jul
(13) |
Aug
|
Sep
|
Oct
|
Nov
(5) |
Dec
|
| 2016 |
Jan
|
Feb
(2) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(3) |
| 2018 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(6) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2019 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(10) |
Jun
(1) |
Jul
|
Aug
|
Sep
|
Oct
(2) |
Nov
|
Dec
|
| 2021 |
Jan
(9) |
Feb
|
Mar
|
Apr
|
May
(2) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2023 |
Jan
|
Feb
|
Mar
(3) |
Apr
|
May
(2) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2024 |
Jan
|
Feb
(1) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2025 |
Jan
|
Feb
|
Mar
|
Apr
(2) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Dalal, M. (ARC-TI)[K. W. S. LLC]
<mic...@na...> - 2025-04-28 18:15:46
|
Hi Christopher,
Thanks for your interest in PLEXIL, and for providing an example plan. You ask a good question.
If you are using release 4.6 of PLEXIL (the releases/plexil-4.6 branch), which is its officially supported version, your plan will produce a runtime error because of the assignment conflict, and the way to deconflict the assignments is by adding a Priority clause to each assignment node. I’ve attached an example plan, which also prints the result.
Note that both assignments execute, at the same logical time (execution cycle) but in the prioritized order. The higher priority node (lower number) will execute *first*, which in this case means that the lower priority node (higher number) will be the final value. I realize this may be unintuitive!
If you are using Release 6 (the releases/plexil-6) or ‘develop’ branch, the situation is different – your original plan will execute and the assignments will occur in unspecified order. I can elaborate on this and explore options if needed.
Let us know if you have further questions.
Best,
Michael
K. Michael Dalal
Autonomous Systems and Robotics, Code TI
KBR Inc. at NASA Ames Research Center
Moffett Field, CA 94035
* Opinions expressed herein are my own *
On 4/25/25, 4:34 AM, "Christopher Gaudig via plexil-support" <ple...@li...<mailto:ple...@li...>> wrote:
Hi PLEXIL devs and users!
I was wondering how one could solve "variable contention" in cases where 2 or more concurrent blocks want so set a global "flag" variable to a value of 1 but I cannot guarantee that this writing to the variable will always happen at non-equal points in time.
Short simplified example:
MyConcurrence:
Concurrence
{
Integer flag = 0;
BlockA:
{
Wait 3.0, 1.0;
flag = 1;
}
BlockB:
{
Wait 3.0, 1.0;
flag = 1;
}
}
PlexilExec.cc handles these conflicts by using a VariableConflictSet and a comment mentions a "priority" there. Is there a way to give a higher priority to the assignment in BlockA ?
Thanks for your help!
Regards from Germany,
Christopher
[cid:image001.png@01DBB82E.C638CFE0]
Christopher Gaudig
Software Developer
Subsea Structures
T +4942120095703
|
|
From: Christopher G. <cg...@ro...> - 2025-04-25 11:33:53
|
Hi PLEXIL devs and users!
I was wondering how one could solve "variable contention" in cases where 2 or more concurrent blocks want so set a global "flag" variable to a value of 1 but I cannot guarantee that this writing to the variable will always happen at non-equal points in time.
Short simplified example:
MyConcurrence:
Concurrence
{
Integer flag = 0;
BlockA:
{
Wait 3.0, 1.0;
flag = 1;
}
BlockB:
{
Wait 3.0, 1.0;
flag = 1;
}
}
PlexilExec.cc handles these conflicts by using a VariableConflictSet and a comment mentions a "priority" there. Is there a way to give a higher priority to the assignment in BlockA ?
Thanks for your help!
Regards from Germany,
Christopher
[cid:34a17f52-a99b-4448-a419-919a3ff7484a]
Christopher Gaudig
Software Developer
Subsea Structures
T +4942120095703
|
|
From: Dalal, M. (ARC-TI)[K. W. S. LLC]
<mic...@na...> - 2024-02-01 19:44:14
|
Test message – a brief reply would be helpful if you received this. Thanks, Mike |
|
From: Fry, C. R. {C. (ARC-TI)[K. W. S. LLC]
<chu...@na...> - 2023-05-15 18:00:11
|
[BCC'd internal dev team] Hi, sorry for the very delayed response. IPC is a third-party module whose origins predate the Raspberry Pi and the 64-bit Arm architecture. It is no longer maintained by its creators. In recent years, we've seen an increasing number of build issues caused by IPC's quite dated C code and build system. The multi-exec, robosim, and simulator examples depend on IPC. Several other examples can be built and executed without it. Unfortunately the top level Makefile doesn't have a convenience target to build the core components without IPC. If you are willing to wade into the IPC build, the file plexil/src/third-party/ipc/src/formatters.h defines IPC_ALIGN for a variety of platforms. If you do come up with a working definition, please send us the diffs so we can incorporate them into the distribution. I am sorry we are not able to offer more help with this issue. I've created an internal issue to find a replacement for IPC. -- Chuck Charles R. (Chuck) Fry - he/him/his chu...@na...<mailto:chu...@na...> Qualified Technical Services Inc. at Ames Research Center Code TI Not speaking for QTS, KBR Wyle, Code TI, or NASA. On 5/5/23, 8:49 PM, "Erich Geisert" <eri...@gm...<mailto:eri...@gm...>> wrote: CAUTION: This email originated from outside of NASA. Please take care when clicking links or opening attachments. Use the "Report Message" button to report suspicious messages to the NASA SOC. Hello, I've been trying to install PLEXIL onto a new Raspberry Pi 4 model with 8gb ram, running the lastest Ubuntu, and I've run into an issue that I've been beating my head against for the past couple of days. The issue in question is here: make[5]: Entering directory '/home/user/plexil/src/third-party/ipc/src' gcc -Wall -Wstrict-prototypes -Wnested-externs -Wmissing-prototypes -Wmissing-declarations -O2 -fPIC -I. -I/home/user/plexil/include -DREDHAT_52 -DREDHAT_6 -DREDHAT_71 -DTHREADED -c -fpic -o /home/user/plexil/src/third-party/ipc/sharedObj/Linux-6.2/datamsg.o datamsg.c datamsg.c: In function ‘x_ipc_dataMsgCreate’: datamsg.c:1162:40: error: ‘IPC_ALIGN’ undeclared (first use in this function) 1162 | dataMsg->alignment = (ALIGNMENT_TYPE)IPC_ALIGN; I believe it has something to do with the compiler not linking files appropriately, but I do not know how to solve this issue. I've installed every library that I can think of. At this point. Has this issue ever come up in the past, and if so, how was it solved? Thank you for reading this, Erich Geisert |
|
From: Erich G. <eri...@gm...> - 2023-05-06 03:49:03
|
Hello, I've been trying to install PLEXIL onto a new Raspberry Pi 4 model with 8gb ram, running the lastest Ubuntu, and I've run into an issue that I've been beating my head against for the past couple of days. The issue in question is here: make[5]: Entering directory '/home/user/plexil/src/third-party/ipc/src' gcc -Wall -Wstrict-prototypes -Wnested-externs -Wmissing-prototypes -Wmissing-declarations -O2 -fPIC -I. -I/home/user/plexil/include -DREDHAT_52 -DREDHAT_6 -DREDHAT_71 -DTHREADED -c -fpic -o /home/user/plexil/src/third-party/ipc/sharedObj/Linux-6.2/datamsg.o datamsg.c datamsg.c: In function ‘x_ipc_dataMsgCreate’: datamsg.c:1162:40: error: ‘IPC_ALIGN’ undeclared (first use in this function) 1162 | dataMsg->alignment = (ALIGNMENT_TYPE)IPC_ALIGN; I believe it has something to do with the compiler not linking files appropriately, but I do not know how to solve this issue. I've installed every library that I can think of. At this point. Has this issue ever come up in the past, and if so, how was it solved? Thank you for reading this, Erich Geisert |
|
From: Dalal, M. (ARC-TI)[K. W. S. LLC]
<mic...@na...> - 2023-03-20 16:43:00
|
Hi Martin, We appreciate your interest in and use of PLEXIL, and any contributions you are willing to make! Let me suggest an alternate approach for submitting your patches. Fork the PLEXIL repository, put the patch on a branch in the forked repo, and then submit a GitHub pull request from the fork’s branch to the target branch on the server that you based the patch on, e.g. releases/plexil-4.6. This may be easier than creating patch files, and is a more standard workflow for GitHub. Indeed we need to establish and document a process for external contributions. Best, Mike K. Michael Dalal Lead, OceanWATERS (github.com/nasa/ow_simulator) Autonomous Systems and Robotics, Code TI KBR Inc. at NASA Ames Research Center * Opinions expressed herein are only my own * On 3/20/23, 9:11 AM, "Fry, Charles R. {Chuck} (ARC-TI)[KBR Wyle Services, LLC] via plexil-support" <ple...@li...<mailto:ple...@li...>> wrote: Hello Martin. The PLEXIL team intended that users could write their own applications using the interfaces in the app-framework library. We realize this is not as well documented as it should be. PLEXIL is intended to be compliant with C++ and POSIX standards, and is developed and maintained on multiple Linux distributions. Which Linux distro were you using, and on what hardware? We would be interested in reviewing and possibly incorporating your changes. Could you please send them to us as patch files? Thank you very much! -- Chuck Charles R. (Chuck) Fry - he/him/his chu...@na...<mailto:chu...@na...> Qualified Technical Services Inc. at Ames Research Center Code TI Not speaking for QTS, KBR Wyle, Code TI, or NASA. On 3/20/23, 4:24 AM, "Martin Fritsche" <mfr...@ro...<mailto:mfr...@ro...>> wrote: Hi, I tried to use Plexil as a library and link it to my own application (not using UniversalExec). This seems not to be the usual way, but I managed to do it with reading some code of UniversalExec and the library. Still, I had to make a few patches to minimize crashing and remove some warnings. Are you interested in those? They are based on Plexil 4.6d0 and at least are functional with Linux (other OSs probably are a problem for one of them). If you are interested, what is the best way to make them available to you? I couldn’t find instructions for contributing. Best, Martin Martin Fritsche Software Engineer Subsea Solutions Creation Center Phone +49-421-200957-09 Mobile +49-151-2645-2573 mfr...@ro...<mailto:mfr...@ro...> ROSEN Creation Center GmbH Branch Office Bremen Arberger Hafendamm 22 28309 Bremen · GERMANY www.rosen-group.com<https://gcc02.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.rosen-group.com%2F&data=05%7C01%7Cmichael.dalal%40nasa.gov%7C1c466ad93af2460522d508db295dc22a%7C7005d45845be48ae8140d43da96dd17b%7C0%7C0%7C638149254909249259%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=pSBCU7FPqpjJM5ErY5B2CdEgykka458D1x6V1zbbaD8%3D&reserved=0> [Image removed by sender.] This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden. This e-mail address is provided for business correspondence only. It is not to be used for promotional or bulk mail, or given or sold to a third party for any purpose. |
|
From: Fry, C. R. {C. (ARC-TI)[K. W. S. LLC]
<chu...@na...> - 2023-03-20 16:11:17
|
Hello Martin. The PLEXIL team intended that users could write their own applications using the interfaces in the app-framework library. We realize this is not as well documented as it should be. PLEXIL is intended to be compliant with C++ and POSIX standards, and is developed and maintained on multiple Linux distributions. Which Linux distro were you using, and on what hardware? We would be interested in reviewing and possibly incorporating your changes. Could you please send them to us as patch files? Thank you very much! -- Chuck Charles R. (Chuck) Fry - he/him/his chu...@na...<mailto:chu...@na...> Qualified Technical Services Inc. at Ames Research Center Code TI Not speaking for QTS, KBR Wyle, Code TI, or NASA. On 3/20/23, 4:24 AM, "Martin Fritsche" <mfr...@ro...<mailto:mfr...@ro...>> wrote: Hi, I tried to use Plexil as a library and link it to my own application (not using UniversalExec). This seems not to be the usual way, but I managed to do it with reading some code of UniversalExec and the library. Still, I had to make a few patches to minimize crashing and remove some warnings. Are you interested in those? They are based on Plexil 4.6d0 and at least are functional with Linux (other OSs probably are a problem for one of them). If you are interested, what is the best way to make them available to you? I couldn’t find instructions for contributing. Best, Martin Martin Fritsche Software Engineer Subsea Solutions Creation Center Phone +49-421-200957-09 Mobile +49-151-2645-2573 mfr...@ro...<mailto:mfr...@ro...> ROSEN Creation Center GmbH Branch Office Bremen Arberger Hafendamm 22 28309 Bremen · GERMANY www.rosen-group.com<https://gcc02.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.rosen-group.com%2F&data=05%7C01%7CChuck.Fry%40nasa.gov%7C6d886cc1a1bd48fd29a708db2935ae4c%7C7005d45845be48ae8140d43da96dd17b%7C0%7C0%7C638149082817195651%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=guzZjIXNnkfYREai%2BpseBhDPwpV%2FuG%2BHRxdIA%2FZgZbE%3D&reserved=0> [Image removed by sender.] This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden. This e-mail address is provided for business correspondence only. It is not to be used for promotional or bulk mail, or given or sold to a third party for any purpose. |
|
From: Martin F. <mfr...@ro...> - 2023-03-20 11:24:17
|
Hi, I tried to use Plexil as a library and link it to my own application (not using UniversalExec). This seems not to be the usual way, but I managed to do it with reading some code of UniversalExec and the library. Still, I had to make a few patches to minimize crashing and remove some warnings. Are you interested in those? They are based on Plexil 4.6d0 and at least are functional with Linux (other OSs probably are a problem for one of them). If you are interested, what is the best way to make them available to you? I couldn't find instructions for contributing. Best, Martin Martin Fritsche Software Engineer Subsea Solutions Creation Center Phone +49-421-200957-09 Mobile +49-151-2645-2573 mfr...@ro...<mailto:mfr...@ro...> ROSEN Creation Center GmbH Branch Office Bremen Arberger Hafendamm 22 28309 Bremen * GERMANY www.rosen-group.com<http://www.rosen-group.com> [https://pictures.rosen-group.com/signatures/ROSEN_Logo_Transparent_160x48.png] This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden. This e-mail address is provided for business correspondence only. It is not to be used for promotional or bulk mail, or given or sold to a third party for any purpose. |
|
From: Dalal, M. (ARC-TI)[K. W. S. LLC]
<mic...@na...> - 2021-05-20 01:02:13
|
Great, and my next experiment confirmed that the actual email address is:
ple...@li...
Caroline was missing the 'lists'.
I also learned that anyone can add themselves to this list, as you saw my personal email get added. Not sure this is good.
I also discovered that the 'plexil-discussion' list has been used sparsely and in only two years ever, 2008 and 2017.
Also, that every message ever sent to these lists is archived on Sourceforge.
I propose that we eliminate these lists. The concept seems so 90s! I think we just a technical support email whose membership is under our control. I propose we use ple...@nx..., assuming that we can update this list, at least with SG's help.
On the other hand, if you're fine with the unlimited access plexil-support and/or a barely used plexil-discussion list, I can live with that.
Mike
On 5/19/21, 5:46 PM, "Fry, Charles R. {Chuck} (ARC-TI)[KBR Wyle Services, LLC]" <chu...@na...> wrote:
Look what just showed up in my inbox. -- Chuck
On 5/19/21, 5:44 PM, "sit...@li..." <sit...@li...> wrote:
Subscribed: km...@pa...
|
|
From: Dalal, M. (ARC-TI)[K. W. S. LLC]
<mic...@na...> - 2021-05-20 00:48:09
|
Sorry for the broad distribution -- just a test! |
|
From: Naal, U. (ARC-TI)[K. W. S. LLC] <uss...@na...> - 2021-01-27 18:58:42
|
Thanks Chuck, I did verify that your change did address the problem on my end.
________________________________
From: Fry, Charles R. {Chuck} (ARC-TI)[KBR Wyle Services, LLC] <chu...@na...>
Sent: Wednesday, January 27, 2021 10:07 AM
To: Naal, Ussama (ARC-TI)[KBR Wyle Services, LLC] <uss...@na...>; ple...@li... <ple...@li...>
Subject: Re: [plexil-support] [EXTERNAL] PLEXIL fails to build stating Debug.hh is missing
I've pushed a fix for this problem. Please pull again from the releases/plexil-4 branch off Sourceforge.
If you don't need the 'robosim' example, I suggest that you do 'make tools' instead of 'make' as the last step.
Apologies for the inconvenience.
-- Chuck
On 1/27/21, 9:33 AM, "Fry, Charles R. {Chuck} (ARC-TI)[KBR Wyle Services, LLC] via plexil-support" <ple...@li...<mailto:ple...@li...>> wrote:
I'm able to reproduce this on my platform, so I will have a fix for you later today. Apologies for the error.
-- Chuck Fry
On 1/27/21, 8:18 AM, "Naal, Ussama (ARC-TI)[KBR Wyle Services, LLC] via plexil-support" <ple...@li...<mailto:ple...@li...>> wrote:
I was trying to build PLEXIL off the release-4 branch. I keep getting the following compiler error message (listed below).
I have also tried to build plexil off the 2020-11-17 tag but no success.
Build Commands and Options
source $PLEXIL_HOME/scripts/plexil-setup.sh
cd $PLEXIL_HOME
make src/configure
cd src
./configure CFLAGS="-g -O2" CXXFLAGS="-g -O2" --prefix=$PLEXIL_HOME --disable-static --disable-viewer --enable-ipc
cd $PLEXIL_HOME
make
Compiler Error message:
Total time: 2 seconds
make -C examples/robosim
make[1]: Entering directory '/usr/local/home/unaal/dev/plexil/examples/robosim'
make -C 2DRobotSimulator
make[2]: Entering directory '/usr/local/home/unaal/dev/plexil/examples/robosim/2DRobotSimulator'
g++ -g -O2 -fPIC -Wno-deprecated-declarations -DPIC -I/include -c -o Flags.o Flags.cc
Flags.cc:27:10: fatal error: Debug.hh: No such file or directory
#include "Debug.hh"
^~~~~~~~~~
compilation terminated.
<builtin>: recipe for target 'Flags.o' failed
make[2]: *** [Flags.o] Error 1
make[2]: Leaving directory '/usr/local/home/unaal/dev/plexil/examples/robosim/2DRobotSimulator'
Makefile:36: recipe for target '2DRoboSim' failed
make[1]: *** [2DRoboSim] Error 2
make[1]: Leaving directory '/usr/local/home/unaal/dev/plexil/examples/robosim'
Makefile:84: recipe for target 'robosim' failed
make: *** [robosim] Error 2
Ussama
|
|
From: Dalal, M. (ARC-TI)[K. W. S. LLC]
<mic...@na...> - 2021-01-27 18:10:48
|
Thanks for the quick fix, Chuck. I'll share the solution with the JPL user, try it myself (using 'make tools'), and update the OW installation docs accordingly.
Mike
On 1/27/21, 10:07 AM, "Fry, Charles R. {Chuck} (ARC-TI)[KBR Wyle Services, LLC] via plexil-support" <ple...@li...<mailto:ple...@li...>> wrote:
I've pushed a fix for this problem. Please pull again from the releases/plexil-4 branch off Sourceforge.
If you don't need the 'robosim' example, I suggest that you do 'make tools' instead of 'make' as the last step.
Apologies for the inconvenience.
-- Chuck
On 1/27/21, 9:33 AM, "Fry, Charles R. {Chuck} (ARC-TI)[KBR Wyle Services, LLC] via plexil-support" <ple...@li...<mailto:ple...@li...>> wrote:
I'm able to reproduce this on my platform, so I will have a fix for you later today. Apologies for the error.
-- Chuck Fry
On 1/27/21, 8:18 AM, "Naal, Ussama (ARC-TI)[KBR Wyle Services, LLC] via plexil-support" <ple...@li...<mailto:ple...@li...>> wrote:
I was trying to build PLEXIL off the release-4 branch. I keep getting the following compiler error message (listed below).
I have also tried to build plexil off the 2020-11-17 tag but no success.
Build Commands and Options
source $PLEXIL_HOME/scripts/plexil-setup.sh
cd $PLEXIL_HOME
make src/configure
cd src
./configure CFLAGS="-g -O2" CXXFLAGS="-g -O2" --prefix=$PLEXIL_HOME --disable-static --disable-viewer --enable-ipc
cd $PLEXIL_HOME
make
Compiler Error message:
Total time: 2 seconds
make -C examples/robosim
make[1]: Entering directory '/usr/local/home/unaal/dev/plexil/examples/robosim'
make -C 2DRobotSimulator
make[2]: Entering directory '/usr/local/home/unaal/dev/plexil/examples/robosim/2DRobotSimulator'
g++ -g -O2 -fPIC -Wno-deprecated-declarations -DPIC -I/include -c -o Flags.o Flags.cc
Flags.cc:27:10: fatal error: Debug.hh: No such file or directory
#include "Debug.hh"
^~~~~~~~~~
compilation terminated.
<builtin>: recipe for target 'Flags.o' failed
make[2]: *** [Flags.o] Error 1
make[2]: Leaving directory '/usr/local/home/unaal/dev/plexil/examples/robosim/2DRobotSimulator'
Makefile:36: recipe for target '2DRoboSim' failed
make[1]: *** [2DRoboSim] Error 2
make[1]: Leaving directory '/usr/local/home/unaal/dev/plexil/examples/robosim'
Makefile:84: recipe for target 'robosim' failed
make: *** [robosim] Error 2
Ussama
|
|
From: Fry, C. R. {C. (ARC-TI)[K. W. S. LLC]
<chu...@na...> - 2021-01-27 18:07:24
|
I've pushed a fix for this problem. Please pull again from the releases/plexil-4 branch off Sourceforge.
If you don't need the 'robosim' example, I suggest that you do 'make tools' instead of 'make' as the last step.
Apologies for the inconvenience.
-- Chuck
On 1/27/21, 9:33 AM, "Fry, Charles R. {Chuck} (ARC-TI)[KBR Wyle Services, LLC] via plexil-support" <ple...@li...<mailto:ple...@li...>> wrote:
I'm able to reproduce this on my platform, so I will have a fix for you later today. Apologies for the error.
-- Chuck Fry
On 1/27/21, 8:18 AM, "Naal, Ussama (ARC-TI)[KBR Wyle Services, LLC] via plexil-support" <ple...@li...<mailto:ple...@li...>> wrote:
I was trying to build PLEXIL off the release-4 branch. I keep getting the following compiler error message (listed below).
I have also tried to build plexil off the 2020-11-17 tag but no success.
Build Commands and Options
source $PLEXIL_HOME/scripts/plexil-setup.sh
cd $PLEXIL_HOME
make src/configure
cd src
./configure CFLAGS="-g -O2" CXXFLAGS="-g -O2" --prefix=$PLEXIL_HOME --disable-static --disable-viewer --enable-ipc
cd $PLEXIL_HOME
make
Compiler Error message:
Total time: 2 seconds
make -C examples/robosim
make[1]: Entering directory '/usr/local/home/unaal/dev/plexil/examples/robosim'
make -C 2DRobotSimulator
make[2]: Entering directory '/usr/local/home/unaal/dev/plexil/examples/robosim/2DRobotSimulator'
g++ -g -O2 -fPIC -Wno-deprecated-declarations -DPIC -I/include -c -o Flags.o Flags.cc
Flags.cc:27:10: fatal error: Debug.hh: No such file or directory
#include "Debug.hh"
^~~~~~~~~~
compilation terminated.
<builtin>: recipe for target 'Flags.o' failed
make[2]: *** [Flags.o] Error 1
make[2]: Leaving directory '/usr/local/home/unaal/dev/plexil/examples/robosim/2DRobotSimulator'
Makefile:36: recipe for target '2DRoboSim' failed
make[1]: *** [2DRoboSim] Error 2
make[1]: Leaving directory '/usr/local/home/unaal/dev/plexil/examples/robosim'
Makefile:84: recipe for target 'robosim' failed
make: *** [robosim] Error 2
Ussama
|
|
From: Fry, C. R. {C. (ARC-TI)[K. W. S. LLC]
<chu...@na...> - 2021-01-27 17:32:48
|
I'm able to reproduce this on my platform, so I will have a fix for you later today. Apologies for the error.
-- Chuck Fry
On 1/27/21, 8:18 AM, "Naal, Ussama (ARC-TI)[KBR Wyle Services, LLC] via plexil-support" <ple...@li...<mailto:ple...@li...>> wrote:
I was trying to build PLEXIL off the release-4 branch. I keep getting the following compiler error message (listed below).
I have also tried to build plexil off the 2020-11-17 tag but no success.
Build Commands and Options
source $PLEXIL_HOME/scripts/plexil-setup.sh
cd $PLEXIL_HOME
make src/configure
cd src
./configure CFLAGS="-g -O2" CXXFLAGS="-g -O2" --prefix=$PLEXIL_HOME --disable-static --disable-viewer --enable-ipc
cd $PLEXIL_HOME
make
Compiler Error message:
Total time: 2 seconds
make -C examples/robosim
make[1]: Entering directory '/usr/local/home/unaal/dev/plexil/examples/robosim'
make -C 2DRobotSimulator
make[2]: Entering directory '/usr/local/home/unaal/dev/plexil/examples/robosim/2DRobotSimulator'
g++ -g -O2 -fPIC -Wno-deprecated-declarations -DPIC -I/include -c -o Flags.o Flags.cc
Flags.cc:27:10: fatal error: Debug.hh: No such file or directory
#include "Debug.hh"
^~~~~~~~~~
compilation terminated.
<builtin>: recipe for target 'Flags.o' failed
make[2]: *** [Flags.o] Error 1
make[2]: Leaving directory '/usr/local/home/unaal/dev/plexil/examples/robosim/2DRobotSimulator'
Makefile:36: recipe for target '2DRoboSim' failed
make[1]: *** [2DRoboSim] Error 2
make[1]: Leaving directory '/usr/local/home/unaal/dev/plexil/examples/robosim'
Makefile:84: recipe for target 'robosim' failed
make: *** [robosim] Error 2
Ussama
|
|
From: Dalal, M. (ARC-TI)[K. W. S. LLC]
<mic...@na...> - 2021-01-27 16:56:21
|
PS: Perhaps the PLEXIL installation sequence we give with OceanWATERS (copied below) are no longer valid, or not optimal.
On 1/27/21, 8:54 AM, "Dalal, Michael (ARC-TI)[KBR Wyle Services, LLC] via plexil-support" <ple...@li...<mailto:ple...@li...>> wrote:
Another collaborator at JPL is having the same problem.
I had this problem recently and somehow worked around it by doing a 'make squeaky clean' followed by 'make' in $PLEXIL_HOME, but this did not work for the JPL user.
Mike
On 1/27/21, 8:18 AM, "Naal, Ussama (ARC-TI)[KBR Wyle Services, LLC] via plexil-support" <ple...@li...<mailto:ple...@li...>> wrote:
I was trying to build PLEXIL off the release-4 branch. I keep getting the following compiler error message (listed below).
I have also tried to build plexil off the 2020-11-17 tag but no success.
Build Commands and Options
source $PLEXIL_HOME/scripts/plexil-setup.sh
cd $PLEXIL_HOME
make src/configure
cd src
./configure CFLAGS="-g -O2" CXXFLAGS="-g -O2" --prefix=$PLEXIL_HOME --disable-static --disable-viewer --enable-ipc
cd $PLEXIL_HOME
make
Compiler Error message:
Total time: 2 seconds
make -C examples/robosim
make[1]: Entering directory '/usr/local/home/unaal/dev/plexil/examples/robosim'
make -C 2DRobotSimulator
make[2]: Entering directory '/usr/local/home/unaal/dev/plexil/examples/robosim/2DRobotSimulator'
g++ -g -O2 -fPIC -Wno-deprecated-declarations -DPIC -I/include -c -o Flags.o Flags.cc
Flags.cc:27:10: fatal error: Debug.hh: No such file or directory
#include "Debug.hh"
^~~~~~~~~~
compilation terminated.
<builtin>: recipe for target 'Flags.o' failed
make[2]: *** [Flags.o] Error 1
make[2]: Leaving directory '/usr/local/home/unaal/dev/plexil/examples/robosim/2DRobotSimulator'
Makefile:36: recipe for target '2DRoboSim' failed
make[1]: *** [2DRoboSim] Error 2
make[1]: Leaving directory '/usr/local/home/unaal/dev/plexil/examples/robosim'
Makefile:84: recipe for target 'robosim' failed
make: *** [robosim] Error 2
Ussama
|
|
From: Dalal, M. (ARC-TI)[K. W. S. LLC]
<mic...@na...> - 2021-01-27 16:53:50
|
Another collaborator at JPL is having the same problem.
I had this problem recently and somehow worked around it by doing a 'make squeaky clean' followed by 'make' in $PLEXIL_HOME, but this did not work for the JPL user.
Mike
On 1/27/21, 8:18 AM, "Naal, Ussama (ARC-TI)[KBR Wyle Services, LLC] via plexil-support" <ple...@li...<mailto:ple...@li...>> wrote:
I was trying to build PLEXIL off the release-4 branch. I keep getting the following compiler error message (listed below).
I have also tried to build plexil off the 2020-11-17 tag but no success.
Build Commands and Options
source $PLEXIL_HOME/scripts/plexil-setup.sh
cd $PLEXIL_HOME
make src/configure
cd src
./configure CFLAGS="-g -O2" CXXFLAGS="-g -O2" --prefix=$PLEXIL_HOME --disable-static --disable-viewer --enable-ipc
cd $PLEXIL_HOME
make
Compiler Error message:
Total time: 2 seconds
make -C examples/robosim
make[1]: Entering directory '/usr/local/home/unaal/dev/plexil/examples/robosim'
make -C 2DRobotSimulator
make[2]: Entering directory '/usr/local/home/unaal/dev/plexil/examples/robosim/2DRobotSimulator'
g++ -g -O2 -fPIC -Wno-deprecated-declarations -DPIC -I/include -c -o Flags.o Flags.cc
Flags.cc:27:10: fatal error: Debug.hh: No such file or directory
#include "Debug.hh"
^~~~~~~~~~
compilation terminated.
<builtin>: recipe for target 'Flags.o' failed
make[2]: *** [Flags.o] Error 1
make[2]: Leaving directory '/usr/local/home/unaal/dev/plexil/examples/robosim/2DRobotSimulator'
Makefile:36: recipe for target '2DRoboSim' failed
make[1]: *** [2DRoboSim] Error 2
make[1]: Leaving directory '/usr/local/home/unaal/dev/plexil/examples/robosim'
Makefile:84: recipe for target 'robosim' failed
make: *** [robosim] Error 2
Ussama
|
|
From: Naal, U. (ARC-TI)[K. W. S. LLC] <uss...@na...> - 2021-01-27 16:17:55
|
I was trying to build PLEXIL off the release-4 branch. I keep getting the following compiler error message (listed below).
I have also tried to build plexil off the 2020-11-17 tag but no success.
Build Commands and Options
source $PLEXIL_HOME/scripts/plexil-setup.sh
cd $PLEXIL_HOME
make src/configure
cd src
./configure CFLAGS="-g -O2" CXXFLAGS="-g -O2" --prefix=$PLEXIL_HOME --disable-static --disable-viewer --enable-ipc
cd $PLEXIL_HOME
make
Compiler Error message:
Total time: 2 seconds
make -C examples/robosim
make[1]: Entering directory '/usr/local/home/unaal/dev/plexil/examples/robosim'
make -C 2DRobotSimulator
make[2]: Entering directory '/usr/local/home/unaal/dev/plexil/examples/robosim/2DRobotSimulator'
g++ -g -O2 -fPIC -Wno-deprecated-declarations -DPIC -I/include -c -o Flags.o Flags.cc
Flags.cc:27:10: fatal error: Debug.hh: No such file or directory
#include "Debug.hh"
^~~~~~~~~~
compilation terminated.
<builtin>: recipe for target 'Flags.o' failed
make[2]: *** [Flags.o] Error 1
make[2]: Leaving directory '/usr/local/home/unaal/dev/plexil/examples/robosim/2DRobotSimulator'
Makefile:36: recipe for target '2DRoboSim' failed
make[1]: *** [2DRoboSim] Error 2
make[1]: Leaving directory '/usr/local/home/unaal/dev/plexil/examples/robosim'
Makefile:84: recipe for target 'robosim' failed
make: *** [robosim] Error 2
Ussama
|
|
From: Fry, C. R. {C. (ARC-TI)[K. W. S. LLC]
<chu...@na...> - 2021-01-26 00:32:08
|
Hello Artur. We intend to do one final release of the 'releases/plexil-4' branch, in the next month or so. At that time the plexil-4 branch will be frozen. There is ongoing work on a significantly updated version on the 'develop' branch, but it cannot be considered stable at this time.
At the moment the PLEXIL team at NASA Ames consists of two people. We are both actively using PLEXIL in projects, but maintaining the open source release is not something we are paid to do. Apologies in advance for the delays.
-- Chuck Fry chu...@na...
QTS Inc. at NASA Ames Code TI
On 1/25/21, 4:22 PM, "Artur Miller" <am...@ro...<mailto:am...@ro...>> wrote:
Hello,
in the current release of Plexil deprecated/removed C++ features like Dynamic exception specification are still used. I have seen, that you are actively working on this. Are you planning to make a new release soon?
Best regards
Artur Miller
|
|
From: Artur M. <am...@ro...> - 2021-01-25 14:04:02
|
Hello, in the current release of Plexil deprecated/removed C++ features like Dynamic exception specification are still used. I have seen, that you are actively working on this. Are you planning to make a new release soon? Best regards Artur Miller |
|
From: Fry, C. R. {C. (ARC-TI)[S. INC] <chu...@na...> - 2019-10-11 20:14:42
|
Sorry to hear you're having difficulties. Did you set PLEXIL_HOME as the instructions suggested? Running PLEXIL -------------- 1. Set up your environment. The PLEXIL shell scripts depend on the setting of PLEXIL_HOME, and for convenience you may wish to add the PLEXIL scripts and binaries to your shell's path. This example is for the Bourne/bash shells or similar. export PLEXIL_HOME='/location/of/plexil' . $PLEXIL_HOME/scripts/plexil-setup.sh You may wish to add these two lines to your shell init file. -- Chuck From: Marsel Omeri <Mar...@ua...> Date: Friday, October 11, 2019 at 12:31 PM To: "ple...@li..." <ple...@li...> Subject: [EXTERNAL] [plexil-support] plexilc: command not found Hello, I recently tried to install PLEXIL in a 64 bit laptop with Ubuntu 18.04. I followed the instructions in README to build it and it seems that everything goes fine. While I tried to test the basic examples, it gives me the following error: plexilc: command not found Apparently none of PLEXIL commands is working. Could you give me some help how to fix this. Thank you, Marsel |
|
From: Marsel O. <Mar...@ua...> - 2019-10-11 19:30:57
|
Hello, I recently tried to install PLEXIL in a 64 bit laptop with Ubuntu 18.04. I followed the instructions in README to build it and it seems that everything goes fine. While I tried to test the basic examples, it gives me the following error: plexilc: command not found Apparently none of PLEXIL commands is working. Could you give me some help how to fix this. Thank you, Marsel |
|
From: Dalal, M. (ARC-TI)[S. INC] <mic...@na...> - 2019-06-14 22:48:51
|
Hi Martin,
Please try the latest Plexil revision 5108 for a fix to the key bug that prevented plan execution from the viewer, and other fixes. We hope to do even more soon. And a belated thanks for your patch file. We used a variation of your socket fix, though didn't have luck with the SwingUtilities change; we worked with the newest revision though.
Best,
Mike
On 5/24/19, 7:21 AM, "Martin Fritsche" <mar...@un...> wrote:
Hi Michael,
I was able to fix the problem with the not closing window and the failed
connection to the viewer.
But I had to revert to SVN revision 5023 and change a few lines of code.
And I didn't test it very much. So I'm not sure if it is a good or bad
change but it works for me and maybe it can help someone else.
Best,
Martin
Dalal, Michael (ARC-TI)[SGT, INC] schrieb am 04.05.2019 um 01:18:
> Hi Martin,
>
> Thanks for your message to plexil-support and your interest in PLEXIL.
>
> I was able to reproduce the problems you reported with the Plexil Viewer. The entry I have just added and committed in plexil-4/CAVEATS sumarizes the situation:
>
> * May 3, 2019. For a while now, the Plexil Viewer is not in a good working
> state. It has not been actively supported in years, and has a variety of
> problems. PLEXIL is still in strong use, in its command line form.
>
> The example plan will run fine without the viewer:
>
> plexiltest -p DriveToTarget.plx -s scripts/DriveToTarget.psx
>
> You can get detailed information about execution state by entering the desired flags in your Debug.cfg file -- see the section on executing PLEXIL plans on Sourceforge. This is how we have been running PLEXIL and debugging plans. At the moment we don't have the budget and staff needed to work on the PLEXIL viewer. Hopefully we will at some point, but in the mean time you are encouraged to debug/improve the Viewer yourself if you are so inclined. We would welcome any fixes or enhancements to it from the PLEXIL community. We hope that PLEXIL otherwise meets your needs.
>
> Best,
> Mike
>
> K. Michael Dalal
> SGT Inc. at NASA Ames Research Center
> --Opinions expressed herein are my own--
>
>
>
|
|
From: Martin F. <mar...@un...> - 2019-05-24 14:21:06
|
Hi Michael, I was able to fix the problem with the not closing window and the failed connection to the viewer. But I had to revert to SVN revision 5023 and change a few lines of code. And I didn't test it very much. So I'm not sure if it is a good or bad change but it works for me and maybe it can help someone else. Best, Martin Dalal, Michael (ARC-TI)[SGT, INC] schrieb am 04.05.2019 um 01:18: > Hi Martin, > > Thanks for your message to plexil-support and your interest in PLEXIL. > > I was able to reproduce the problems you reported with the Plexil Viewer. The entry I have just added and committed in plexil-4/CAVEATS sumarizes the situation: > > * May 3, 2019. For a while now, the Plexil Viewer is not in a good working > state. It has not been actively supported in years, and has a variety of > problems. PLEXIL is still in strong use, in its command line form. > > The example plan will run fine without the viewer: > > plexiltest -p DriveToTarget.plx -s scripts/DriveToTarget.psx > > You can get detailed information about execution state by entering the desired flags in your Debug.cfg file -- see the section on executing PLEXIL plans on Sourceforge. This is how we have been running PLEXIL and debugging plans. At the moment we don't have the budget and staff needed to work on the PLEXIL viewer. Hopefully we will at some point, but in the mean time you are encouraged to debug/improve the Viewer yourself if you are so inclined. We would welcome any fixes or enhancements to it from the PLEXIL community. We hope that PLEXIL otherwise meets your needs. > > Best, > Mike > > K. Michael Dalal > SGT Inc. at NASA Ames Research Center > --Opinions expressed herein are my own-- > > > |
|
From: Martin F. <mar...@un...> - 2019-05-23 12:38:07
|
Hi Mike, I just wanted to report that the workaround does its job. Thank you very much for your help. Best, Martin |
|
From: Dalal, M. (ARC-TI)[S. INC] <mic...@na...> - 2019-05-20 16:10:20
|
Hi Martin,
Comments inserted...
On 5/20/19, 5:24 AM, "Martin Fritsche" <mar...@un...> wrote:
[snip]
OK, it seems this proofpoint stuff broke the link. I was referring to
the wiki page "Plexil_Reference" section "Sequence" where it says:
Actually it did get me to the right page, but maybe not the right section.
> If any action fails (i.e. terminates with status FAILURE), the
> Sequence also terminates with status FAILURE.
Therefore I was thinking that sending COMMAND_FAILED would be sufficient
to terminate the sequence with FAILURE. Seems it is not. :-)
The "action failure" here is not command failure, but node failure.
[snip]
OK, the second code block in Resource_Model#Command_Handles was very
helpful. I thought this was relevant only when using resources.
I agree, and I'd like to move that to the command documentation. It's always relevant with commands.
Now my plan is:
Command load_waypoints(String filename);
LoadMission :
{
{
PostCondition Self.command_handle == COMMAND_SUCCESS;
load_waypoints("file.name");
}
}
Which works as expected if I don't send COMMAND_SENT_TO_SYSTEM in my
command execution. If I do, the section is left before the command
finishes and it always fails.
How to handle this?
You're on the right track. The problem now is that the command does not have enough time to finish.
When I write SynchronousCommand load_waypoints("file.name"); instead, I
get an error message from plexilexec:
> ERROR: failtest.ple:13:1: createExpression: Node BLOCK__0 is not a
> Command node ExecApplication::addPlan: Plan parser error:
> createExpression: Node BLOCK__0 is not a Command node
This should have worked. I reproduced the problem and have submitted a bug report. In the mean time, there is an easy workaround, especially since SynchronousCommand is just syntactic sugar. You could get a finer level of control without using it. Simply adding an End condition will help:
Command load_waypoints(String filename);
LoadMission :
{
{
// Add any other handles you may send to the disjunction.
EndCondition (Self.command_handle == COMMAND_SUCCESS ||
Self.command_handle == COMMAND_FAILED);
PostCondition Self.command_handle == COMMAND_SUCCESS;
load_waypoints("file.name");
}
}
Now the node waits for handles of interest. There's no timeout, however, so the node could potentially hang the executive. Maybe this is not a concern if load_waypoints is always fast. Otherwise you could add a time expression to the disjunction in the End condition, something like Lookup(time) > LoadMission.START + LoadWaypointTimeout.
> Please let us know if you run into further difficulty. We'll try to
> improve the Command documentation based on your feedback.
Thanks, I will. If you improve the documentation based on my lack of
understanding you will have the best documentation ever ;-)
Your feedback is certainly helpful!
Best,
Mike
|