1. What is the correct pronunciation of “Gedae”?
2. How can Gedae provide a faster route to more efficient code?
3. How does Gedae improve maintenance (ease of use, cost) as well as life-cycle benefits?
4. What companies have you work for in the past?
5. Isn’t your tool for modeling? We already have one of those.
6. What’s so special about your product?
7. What all happens in your “Compile Application” step?
8. With respect to hardware independence, what’s involved in moving an application built in Gedae from one hardware platform to another?
9. How many processors can Gedae handle?
10. Can Gedae work with tools like UML?
11. Can Gedae work with VSIPL++? Or other third party libraries
12. How does Gedae improve the efficiency of a project team?
13. How easy is it to convert Matlab code into a Gedae graph?
14. What Analysis Tools are included in Gedae?
15. What kind of training do you provide?
16. What application areas does Gedae work in?
17. Can Gedae’s simulation product run in real-time?
18. Can a user override the compile passes?
19. Is documentation generated from Gedae?
20. Does Gedae provide an executable view of the application?

Our company name as well as our software environment are pronounced “JEE-day”. The GE letters on the front go back to the days of General Electric Aerospace, which was acquired by Martin Marietta, and after a merger, is known today as Lockheed Martin.

Gedae’s graphical language and algorithm library provide the path to rapidly developing applications. Unlike traditional development processes, Gedae allows for design and simulation to be immediately followed by setting of partitions and mapping of parameters. Gedae’s multiprocessor compiler then creates the application through autocoding, so no reprogramming in multi-processor code is necessary. Powerful debug and analysis tools allow for rapid changes and a true, iterative development process.

Gedae has in-depth debug and analysis tools which make future modifications and enhancements much easier than working within voluminous code. Also, since Gedae allows for the targeting of multiple hardware platforms, there is little effort needed to port to different, existing hardware, or to take advantage of more powerful hardware when it comes on the market.

We have worked for companies like Lockheed Martin and the Air Force Research Lab in the US, and with Selex, BAE Systems, and Thales in Europe. We can send you some information on some of these projects, or point you to papers on our site. Our Selex relationship goes back to 1999, and Gedae is the environment chosen for the Captor Program, which is going to be used by the Eurofighter fleet. This is quite a large system, but by using Gedae, Selex-SEAS has saved large sums of money in both hardware and personnel expenditures We also have a teaming agreement in place with IBM based on the Cell Broadband Engine and our software expertise in programming multicore systems.

That’s not surprising, but is your modeling tool going to build your software, too? Doing your designing, developing and building (Gedae will auto-code a deployable application) in Gedae’s Common Development Environment will allow you to target any single or multiprocessor hardware you like, providing a true end-to-end solution. But Gedae does have a modeling environment and a simulation environment which utilize the same compiler and language as the application development environment. Finally, how hard is it to get from your models to hardware? It’s faster with Gedae

Gedae allows you to design, test, build and deploy (or ship for deployment) your sensor processing application, all within a common development environment.

Our engineers have built a multiprocessor compiler and a high-level, block diagram language that allows our clients to take advantage of the flexibility of our unique compiler. Functional models can be developed independently of hardware architecture - it is the compiler that takes these two inputs and creates an appropriate, multi-threaded application.

Our tool simply works better, and does much more, than competing products. Applications built in Gedae are more CPU and memory efficient, and more reliable. Also, there are no integration issues outside of the Gedae environment. Finally, the intelligent design and subsequent enhancements to our product over many years has earned us accolades from clients both regarding our software, and also our customer support, which is outstanding.

This is the heart of Gedae. During this step, the compiler takes the functional model, the hardware model, and lightweight libraries and handles multithreading, memory planning, distribution and optimization during multiple compile passes. This is unique because so much is being done at the compile step. The processing concepts and system design pieces can be created upstream and independent of the compiler, which will output an appropriate, multithreaded application for any multi-cpu target.

This is a key differentiator between Gedae and other products. The functionality stays separate and does not need to be modified. If we do not have an existing Board Support Package (BSP) for the new hardware, then a BSP needs to be built. That’s really it – the BSP will allow you to run that same application on different hardware. The same graph will run on the new hardware. The graph will be mapped to the processors on the new hardware, and the application will run identically.

Gedae is not restricted to a specific number of processors. An application in Gedae can be built using any number of processors. One of the key strengths of Gedae is handling systems that involve many processors.

Gedae can run on top of tools like UML. More often than not, clients incorporate Gedae into their engineering process early on to get the most out of both tools.

Gedae can be used in conjunction with VSIPL. In some instances, there are overlaps, so that some of the features of VSIPL are simply not needed because they are handled by Gedae. These include things like memory management.

Gedae promotes an integrated team approach, where typical barriers between team members (algorithm developers, software and hardware engineers, systems engineers, etc.) are removed. As a graph is designed, it continues through the process as a “living and up-to-date” spec, so that slight changes in the software development process do not require a huge effort from the algorithm developers, and the usual back and forth and waiting for modifications is essentially removed. This approach allows all project members to benefit from designing and building an application in Gedae.

We have many defined primitives in our libraries that can quickly replace certain Matlab pieces. For other custom code, Matlab can be converted into Gedae primitives, and that result would be added into Gedae so that any conversion of similar Matlab code in the future would be included as part of the Gedae primitives. Gedae can also make calls to Matlab routines, and this would be transparent to the user.

Gedae has a memory map, a trace table, a flattened graph, data structures, a debug dialog and the ability to add displays to the graph.

Gedae works with clients in a number of ways. We provide initial help with troubleshooting and any other questions that might arise during or after installation. We offer two training courses, an Introductory and Advanced. We highly recommend users taking the intro course to get hands on experience from experts. This course vaults attendees up the learning curve and allows them to return to their offices and effectively start using Gedae. Courses are each one week long.

RADAR, SONAR, Audio, Image Processing, Communications, Electro Optics, LADAR.

Yes it can.

There is a group control box in Gedae where this is controlled, and it is highly recommended that users do not override this.

Design documents and flow documents can be extracted from Gedae.

This is exactly what Gedae does. It is not a design view but rather a true, executable view.