__color__,ticket,summary,component,version,milestone,type,owner,status,created,_changetime,_description,_reporter
3,1,(228) DeviceManager lacks provisions for launching services,ossiecf,,Abeyance,defect,cdietric,new,2007-08-05T23:52:32-0400,2008-04-11T12:59:22-0400,,cdietric
3,2,(230) Implement logging actions in CF,ossiecf,,Abeyance,defect,cdietric,new,2007-08-05T23:53:26-0400,2008-04-11T12:59:55-0400,,cdietric
3,3,(232) Test service connection establishment,ossiecf,,Abeyance,defect,shereef,new,2007-08-05T23:54:39-0400,2008-04-11T13:00:38-0400,,cdietric
3,5,(233) SymbolSyncPoly component has packet discontinuities,component,,Abeyance,defect,hvolos,new,2007-08-05T23:57:40-0400,2009-02-17T14:02:53-0500,,cdietric
3,6,(235) SymbolSyncPoly component has problematic timing loop filter,component,,Abeyance,defect,hvolos,new,2007-08-05T23:58:20-0400,2009-02-17T14:03:27-0500,,cdietric
3,7,(244) MultirateSynchronizer component has trouble acquiring phase synchronization,component,,Abeyance,defect,hvolos,new,2007-08-05T23:59:11-0400,2009-02-17T14:03:36-0500,,cdietric
3,9,(265) devicethatloadedthiscomponentrefports,ossiecf,,Abeyance,enhancement,cdietric,new,2007-08-06T00:00:32-0400,2007-08-06T07:20:46-0400,,tmcguire
3,10,(266) deviceusedbythiscomponentrefports,ossiecf,,Abeyance,enhancement,cdietric,new,2007-08-06T00:01:37-0400,2007-08-06T07:20:23-0400,,tmcguire
3,15,(180) Automate Trac site backup,other,,Infrastructure,task,cdietric,new,2007-08-06T00:07:29-0400,2008-09-21T13:37:54-0400,,cdietric
3,19,(187) Domain Manager configure test fails,ossiecf,,Abeyance,defect,shereef,new,2007-08-06T00:11:29-0400,2012-05-11T04:59:17-0400,,cdietric
3,20,(190) Domain Manager query fails,ossiecf,,Abeyance,defect,shereef,new,2007-08-06T00:12:08-0400,2012-05-11T04:59:17-0400,try again,cdietric
3,24,(215) Supports interfaces not supported,ossiecf,,Abeyance,defect,cdietric,new,2007-08-06T00:15:46-0400,2008-04-11T13:06:34-0400,,cdietric
3,29,(259) Current version of OSSIE framework does not build on OS X due to sched_setscheduler(),ossiecf,,Abeyance,enhancement,cdietric,new,2007-08-06T00:20:05-0400,2008-04-11T13:03:44-0400,,cdietric
4,34,(253) Convert device manager to use SCA compliant device parameters,ossiecf,,Abeyance,defect,shereef,new,2007-08-06T00:25:18-0400,2008-04-11T13:07:24-0400,,cdietric
3,35,(254) Figure out the filesystemname profile element,ossiecf,,Abeyance,defect,shereef,new,2007-08-06T00:26:06-0400,2009-10-30T11:20:12-0400,,cdietric
3,42,(238) Add autofoo for Log Service,ossiecf,,Abeyance,task,cdietric,new,2007-08-06T00:37:37-0400,2008-04-23T17:41:41-0400,,cdietric
3,45,(56) application factory is not re-initialized after an install,ossiecf,,Abeyance,defect,cdietric,new,2007-08-06T00:40:03-0400,2008-04-23T17:42:21-0400,,cdietric
4,86,OWD creates wrong configure.ac file for waveforms,tools,,1.1.8 (OSSIE Eclipse Feature),defect,Snyder.Jason,new,2007-10-19T09:25:59-0400,2011-04-28T09:07:29-0400,OWD generates the component {{{configure.ac}}} for waveforms,jgaeddert
4,90,OWD generates port_list property in .prf.xml,tools,0.6.2-prerelease,Abeyance,defect,unassigned,new,2007-10-24T12:32:37-0400,2008-05-18T09:52:48-0400,"OWD still seems to generate a port_list property that lists all the provides ports in the {{{.prf.xml}}} file. This is redundant as the {{{.scd.xml}}} file has this information. This needs to be removed.
{{{
Returns a sequence of strings with the names of the available Provides ports
samples_in::standardInterfaces.complexShort
}}}",jgaeddert
3,98,Rewrite Application Factory and friends,ossiecf,trunk,Abeyance,defect,cdietric,new,2007-11-16T08:22:28-0500,2008-04-23T17:42:51-0400,"Application Factory is a complex function and needs a complete overhaul in order to address numerous tickets. (#21, #24, #27, #33, #45, #46) Addressing these tickets piece meal is difficult due to the current structure of the software.
A complete re-design of Application factory and Application will greatly increase the capability of OSSIE and make long term maintenance and research much easier.",balister
3,100,Remove Device_impl from framework,ossiecf,trunk,Abeyance,enhancement,cdietric,new,2007-11-25T20:06:17-0500,2008-04-23T17:51:19-0400,"Remove Device_impl.cpp and Device_impl.h from framework.
Impacts any device using the device_impl interface. Inherit directly from the Device class from idl instead. The code in device_impl is not likely to actually be useful for specific implementations.",balister
3,101,Remove Resource_impl from framework,ossiecf,trunk,Abeyance,defect,cdietric,new,2007-11-25T20:15:12-0500,2008-04-23T17:52:01-0400,"Remove Resource_imple.cpp and .h from the framework. Also the _impl for the classes that resource is composed from.
Components will inherit directly from the idl classes.
The goal is to remove all component code from the framework. If it is valuable for a group of people to derive specific components from a base class, the base class should be packaged seperately from the framework code. This seperates framework maintenance from component maintenance.",balister
3,131,problem building new component with timing support,tools,,Abeyance,defect,Snyder.Jason,new,2007-12-05T23:04:51-0500,2010-02-11T12:40:34-0500,"Error listing from make when trying to build new component with 1 uses, 1 provides port and timing support: (note timingStatus.idl is in customInterfaces)
{{{
component20.h:95: error: ISO C++ forbids declaration of ‘timingStatus_u’ with no type
component20.h:95: error: invalid use of ‘::’
component20.h:95: error: expected ‘;’ before ‘*’ token
component20.cpp: In constructor ‘component20_i::component20_i(const char*, omni_condition*)’:
component20.cpp:33: error: ‘dataOut_1’ was not declared in this scope
component20.cpp:33: error: expected type-specifier
component20.cpp:33: error: expected `;'
component20.cpp: In destructor ‘virtual component20_i::~component20_i()’:
component20.cpp:48: error: ‘dataOut_1’ was not declared in this scope
component20.cpp: In member function ‘virtual CORBA::Object* component20_i::getPort(const char*)’:
component20.cpp:74: error: ‘dataOut_1’ was not declared in this scope
make: *** [component20.o] Error 1
}}}",cdietric
3,139,Develop base class to support components,component,trunk,Abeyance,enhancement,cdietric,new,2008-01-04T14:32:38-0500,2009-10-30T11:19:13-0400,"Create a new library (that may or may not be built with ossiecf) that contains base classes used to create components. This should replace all the component code that was contained in the ossiecf libraries.
Doing this should allow components to build without linking the ossiecf and ossieparser libraries, this should reduce a components memory footprint.
",balister
3,141,FileInput needs enhancements,component,trunk,0.9.0 (OSSIE),enhancement,iburbey,new,2008-01-17T11:02:30-0500,2011-04-28T09:54:38-0400,"The FileInput block needs two enhancements:
* The block needs to handle very large files
* Need to accept binary data in both little endian and big endian formats
The data type should be settable via the propertySet interfaces.",balister
5,150,New sound device (was Sound playback does not block when data sent too fast),component,0.7.x,0.9.0 (OSSIE),task,shereef,new,2008-01-24T21:51:06-0500,2011-03-08T11:26:33-0500,"Develop a new sound device for release 0.9.0 that does not rely on ALSA. It should address this problem.
Original description:
The sound playback component drops data when it receives data faster than it can play it back.
This behavior was originally chosen for a waveform where the input data sample rate was set by the USRP and the output rate by the sound car. Since an overrun in this case is a problem, I decided to drop data on overruns.
Now I have a waveform that reads data from a file, processes the data, and sends it to the sound card. Obviously, this leads to drop data and now flow control back to the FileInput block. I plan to change the sound playback routines to block, rather than drop data. We should watch to see if this is a problem for waveforms that receive data from fixed rate sources.",shereef
3,157,omninames and nodebooter take 100% CPU during device startup,ossiecf,trunk,Abeyance,defect,cdietric,new,2008-02-14T09:41:07-0500,2008-04-23T17:53:05-0400,"Omninames and nodebooter are taking 100% CPU during startup on a small form factor system.
I believe this is similar to a problem fixed during component startup where the framework polls omniNames to see when a device has started. On a high speed desktop, this is not noticeable, but on small systems the system spends so much time looking for the name, the device takes a long time to start up.
The (quick) solution is find the code in the device manager that starts the devices and insert a short sleep in the loop.",balister
3,163,Update ALF spectrum plot,tools,trunk,0.9.0 (OSSIE),enhancement,iburbey,new,2008-03-03T07:53:14-0500,2011-04-28T09:53:03-0400,"The ALF plot tool frequency display shows -250 kHz to to 250 kHz. Since ALF does not know the sample rate, it should use a normalized frequency axis markings. This would be much easier to interpret.",balister
2,172,Controller component needed for Sound_in device,component,,0.9.0 (OSSIE),enhancement,cdietric,new,2008-04-10T12:35:59-0400,2011-03-08T11:21:17-0500,A controller component needs to be created for the Sound_in device in the same vein of USRP_Commander for the USRP.,mcarrick
4,188,OEF should warn developer of duplicate names before generating a new node,OSSIE Eclipse Feature,,1.1.8 (OSSIE Eclipse Feature),enhancement,Snyder.Jason,new,2008-05-29T17:22:17-0400,2010-11-22T08:56:19-0500,"Before generating a new node, it would be good to list any other nodes that have identically named device managers and/or devices (this can be done by parsing the dcd files of the existing nodes). The developer should be given the option to continue or cancel. In a multi-node system, device managers and devices all need to have distinct names. Look for tags like the following:
and
GPP1
",cdietric
4,226,CIREN_Install: usrp is not installed with ossie when running build.py,documentation,,Abeyance,defect,shereef,new,2008-07-31T21:05:08-0400,2012-05-11T04:58:50-0400,The USRP install is missing in the current documentation. There was some talk about adding the USRP install into the build.py file for installing ossie. It can certainly be installed manually if added into the CIREN_Install instructions.,jmatzen
4,227,CIREN_Install: ALF errors,ALF,,Abeyance,defect,shereef,new,2008-07-31T21:21:27-0400,2012-05-11T04:58:50-0400,There is no documentation stating that loadAutomationFile.py currently has to be copied from the src directory (ossie-0.6.x/tools/alf) to /sdr/tools/alf. Python Profiler also needs to be installed (apt-get install python-profiler) in order to get ALF running. This may be a combination of documentation mods that are needed as well as build files that may need to be updated.,jmatzen
3,231,Re-write Sound_out,platform,,0.9.0 (OSSIE),defect,jgaeddert,reopened,2008-08-04T16:10:20-0400,2011-03-08T11:33:36-0500,The current Sound_out was written a while ago and needs an update. It is implemented differently than other devices.,mcarrick
3,240,Graceful Death for NodeBooter,system,trunk,0.9.0 (OSSIE),defect,iburbey,new,2008-10-23T13:54:29-0400,2010-11-22T10:42:34-0500,"Right now, in order to terminate NodeBooter, Ctrl-C or kill is used.
Other processes are still in the memory after NodeBooter is killed.",tuan
3,253,ossie_demo crashes,waveform,trunk,0.9.0 (OSSIE),defect,iburbey,new,2009-02-02T15:52:27-0500,2010-11-22T09:38:06-0500,"After installing and uninstalling the ossie_demo waveform several times, the waveform eventually crashes. Initially it may take several (20 or more) install cycles before it crashes, after that it is easier to reproduce.
After the crash, sometimes the TxDemo or the RxDemo components are defunct. We may need to verify our releaseObject behavior.
",caguayog
3,261,Components create too much console output,other,0.7.x,0.9.0 (OSSIE),defect,iburbey,new,2009-04-09T08:16:44-0400,2011-04-28T09:53:34-0400,In r9211 there are lots of std::couts in each components configure method that should be DEBUG mnacros. Leaving them as couts leaves no way for the user to turn off these messages.,balister
4,280,"""recursion depth exceed""",other,trunk,0.9.0 (OSSIE),defect,cdietric,new,2009-09-23T12:58:47-0400,2010-11-22T09:44:37-0500,"I am running into the ""recursion depth exceed"" error message while trying to run gnuradio from the Ubuntu 9.04 image of OSSIE.
Is there anything I can do to get rid of this error?
Thanks,
Ishtiaq.",ishtiaqrouf
3,286,ossie 0.8.0 install bugs,other,trunk,,defect,cdietric,new,2010-02-17T04:43:52-0500,2010-02-17T04:43:52-0500,"Hello
Please make folowing changes:
1:in wavedev/cfg.py:line 212 change to __getpath(/WaveDev/wavedev/generate/generic_preamble)
2:cp reconf to ../wavedev/generate
3:cp SampleMain.cpp to ../templates/basic_ports",mb_nezafati
3,287,can not input default value in property panel,OSSIE Eclipse Feature,0.8.x,,defect,,new,2010-02-25T10:52:05-0500,2010-02-25T10:52:05-0500,I followed the example in the 0.8.0 user guide to create a port and added a property gain. But I can not input the default value. The text box did not change to edit mode. I can not add new or detect a property either,fath
4,294,OSSIE-0.8.0 Lab 6-Remote WaveForm Display (ALF errors),ALF,trunk,,defect,cdietric,new,2010-06-16T15:56:07-0400,2010-06-16T15:56:07-0400," * Computer one is running omniNames and computer two is not as described in lab instructions.
* Firewalls are down
* InitRef in omniORB4.cfg is set to 1.27.0.0.1 on computer one
* InitRef in omniORB4.cfg is set to 192.168.10.31 (computer one's IP) on computer two
* nodeBooter is running on computer one
* c_wavLoader is used to install and begin the wave on computer one
* When ALF is loaded on computer two this error appears:
Failed to narrow the root naming context.
Are the Naming Service and nodeBooter running on 127.0.0.1?
* After clicking the OK box and setting the network host to 192.168.10.31 and clicking Apply, this error appears in the terminal used to launch ALF:
Traceback (most recent call last):
File ""/usr/local/lib/python2.6/dist-packages/alf/namingserviceDialog.py"", line 81, in OnApply
if parent.namingservice[0] not in parent.connections:
AttributeError: 'alfFrame' object has no attribute 'connections'
",aanderson
3,300,"0.8.2 live DVD with OEF 1.1.8, latest User Guide",other,trunk,1.1.8 (OSSIE Eclipse Feature),task,iburbey,new,2010-08-29T17:12:54-0400,2010-11-22T08:50:50-0500,,cdietric
3,301,Document new OEF 1.1.8 features in User Guide,other,trunk,1.1.8 (OSSIE Eclipse Feature),task,Snyder.Jason,new,2010-08-29T17:13:30-0400,2010-11-22T08:53:46-0500,,cdietric
4,303,Component Generation through the OEF,OSSIE Eclipse Feature,trunk,,defect,,new,2010-08-30T11:11:54-0400,2010-08-30T11:11:54-0400,"The problem we are running into is that you can't generate multiple components within the same eclipse session. You can create them and save them, but the Generate Component ""button"" doesn't seem to work for the second component and so on. You have to close eclipse and restart it in order properly generate the component (i.e. generate all of the necessary files).",aschmitt
3,320,Deployment in OEF,other,trunk,1.1.8 (OSSIE Eclipse Feature),defect,Snyder.Jason,new,2011-03-08T11:38:05-0500,2011-03-08T11:38:05-0500,Add option to auto-generate DAS given components and platform.,c2dietric
4,321,USRP's RX_Data_2 Port Not Supported,platform,0.8.x,0.9.0 (OSSIE),defect,cdietric,new,2011-11-15T11:25:41-0500,2011-11-15T11:25:41-0500,"This came in off the ossie-discuss listserv:
I find a bug in USRP.cpp under /ossie/src/ossie-0.8.2/platform/USRP/src directory. At line 80 col 42, rx_data_1_port needs to be changed to rx_data_2_port. That maybe the reasion why RX_Data_2 can not be found in Default_GPP_USRP_node.
",mcarrick