Re: [Discuss OpenCPI] OCPI Assembly Selection

MP
Miller, Peter
Wed, Jun 20, 2018 12:16 PM

We’re using ocpirun only for file driven test stuff. Need the ACI for the real applications.
Can you provide example(s) of ocpiruin command line for -c?

From: aponchak aponchak@office.geontech.com
Sent: Wednesday, June 20, 2018 6:44 AM
To: Miller, Peter PeterM@signalscape.com
Cc: discuss@lists.opencpi.org
Subject: Re: [Discuss OpenCPI] OCPI Assembly Selection

If you're using ocpirun to execute the app, consider specifying the desired container (-c {instance name of component}={container}) for the worker to execute on. This should alleviate the need to rework the OCPI_LIBRARY_PATH, when the path is so broad.

On 2018-06-20 06:24, Miller, Peter <PeterM@signalscape.commailto:PeterM@signalscape.com> wrote:

I believe I am experiencing as pitfall that Adam P. described during training months ago.

export OCPI_LIBRARY_PATH=$OCPI_LIBRARY_PATH:/home/pbmiller/SS_SDR/Frameworks/ocpi.core/exports

OCPI( 8:516.0936): Successfully loaded bitstream file: "/home/pbmiller/SS_SDR/Frameworks/ocpi.core/exports/imports/ocpi.wifiproject/components/transmitter/phy_tx_802dot11g.test/gen/assemblies/phy_tx_802dot11g_0/container-phy_tx_802dot11g_0_xsim_base/target-xsim/phy_tx_802dot11g_0_xsim_base.tar.gz" for simulation

Sincerely,

Peter B. Miller

Potomac: (301) 765-9668

--------------------------- This email and any files transmitted with it are confidential and intended solely for the use of Signalscape, Inc. and the addressed individual or entity. If you have received this email in error please delete it. Information in this email may be subject to the Privacy Act of 1974 and any unauthorized review, use, disclosure, or distribution is strictly prohibited. Any views or opinions presented in this email are solely those of the author and do not necessarily represent those of the company.

-------------- next part --------------

An HTML attachment was scrubbed...

URL: http://lists.opencpi.org/pipermail/discuss_lists.opencpi.org/attachments/20180620/617baccc/attachment.html


discuss mailing list

discuss@lists.opencpi.orgmailto:discuss@lists.opencpi.org

http://lists.opencpi.org/mailman/listinfo/discuss_lists.opencpi.org

--------------------------- This email and any files transmitted with it are confidential and intended solely for the use of Signalscape, Inc. and the addressed individual or entity. If you have received this email in error please delete it. Information in this email may be subject to the Privacy Act of 1974 and any unauthorized review, use, disclosure, or distribution is strictly prohibited. Any views or opinions presented in this email are solely those of the author and do not necessarily represent those of the company.

We’re using ocpirun only for file driven test stuff. Need the ACI for the real applications. Can you provide example(s) of ocpiruin command line for -c? From: aponchak <aponchak@office.geontech.com> Sent: Wednesday, June 20, 2018 6:44 AM To: Miller, Peter <PeterM@signalscape.com> Cc: discuss@lists.opencpi.org Subject: Re: [Discuss OpenCPI] OCPI Assembly Selection If you're using ocpirun to execute the app, consider specifying the desired container (-c {instance name of component}={container}) for the worker to execute on. This should alleviate the need to rework the OCPI_LIBRARY_PATH, when the path is so broad. On 2018-06-20 06:24, Miller, Peter <PeterM@signalscape.com<mailto:PeterM@signalscape.com>> wrote: I believe I am experiencing as pitfall that Adam P. described during training months ago. export OCPI_LIBRARY_PATH=$OCPI_LIBRARY_PATH:/home/pbmiller/SS_SDR/Frameworks/ocpi.core/exports OCPI( 8:516.0936): Successfully loaded bitstream file: "/home/pbmiller/SS_SDR/Frameworks/ocpi.core/exports/imports/ocpi.wifiproject/components/transmitter/phy_tx_802dot11g.test/gen/assemblies/phy_tx_802dot11g_0/container-phy_tx_802dot11g_0_xsim_base/target-xsim/phy_tx_802dot11g_0_xsim_base.tar.gz" for simulation Sincerely, Peter B. Miller Potomac: (301) 765-9668 --------------------------- This email and any files transmitted with it are confidential and intended solely for the use of Signalscape, Inc. and the addressed individual or entity. If you have received this email in error please delete it. Information in this email may be subject to the Privacy Act of 1974 and any unauthorized review, use, disclosure, or distribution is strictly prohibited. Any views or opinions presented in this email are solely those of the author and do not necessarily represent those of the company. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.opencpi.org/pipermail/discuss_lists.opencpi.org/attachments/20180620/617baccc/attachment.html> _______________________________________________ discuss mailing list discuss@lists.opencpi.org<mailto:discuss@lists.opencpi.org> http://lists.opencpi.org/mailman/listinfo/discuss_lists.opencpi.org --------------------------- This email and any files transmitted with it are confidential and intended solely for the use of Signalscape, Inc. and the addressed individual or entity. If you have received this email in error please delete it. Information in this email may be subject to the Privacy Act of 1974 and any unauthorized review, use, disclosure, or distribution is strictly prohibited. Any views or opinions presented in this email are solely those of the author and do not necessarily represent those of the company.