1 / 7

PartitionMaker Design Strategy Ideas

This presentation will probably involve audience discussion, which will create action items. Use PowerPoint to keep track of these action items during your presentation In Slide Show, click on the right mouse button Select “Meeting Minder” Select the “Action Items” tab

loman
Télécharger la présentation

PartitionMaker Design Strategy Ideas

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. This presentation will probably involve audience discussion, which will create action items. Use PowerPoint to keep track of these action items during your presentation • In Slide Show, click on the right mouse button • Select “Meeting Minder” • Select the “Action Items” tab • Type in action items as they come up • Click OK to dismiss this box • This will automatically create an Action Item slide at the end of your presentation with your points entered. PartitionMaker Design Strategy Ideas Rodrigo Coura Torres

  2. Summary • System Design (Draft Version). • Non-Interactive user mode approach (Draft Version). • Conclusions

  3. Create LVL2 Partition R=8, S=2, U=30 Create 8 ROSs Create 30 L2PU Create 2 L2SV L2SV Component ROS Component L2PU Component Native Language Functionalities Development Design • Multi-level approach. • In the lowest level, there will be the DAQ/HLT-I components, organized as: • Ordinary: ROS, L2SV, L2PU, SFI, DFM, etc. • Containers: Segments and partitions. • Higher level methods will combine these components and their functionalities to generate partitions. • Opportunity to work with high or low level functions, according to knowledge / need.

  4. Development Design • Should be an interface declaring common methods that will be called by the higher level functions. • Each component is responsible to define its behavior within the PartitionMaker, by implementing this interface. • Advantages: • Simpler to implement. • Easy addition of plug-ins. • Workload can be split among many developers. Fast Development Cycle!

  5. Ideas for the Non-Interactive Interface • Integrated working environment, like PAW, ROOT, Matlab, etc. • It should provide access to all the PartitionMaker functionalities. • After create / modify the partition’s components, an export function should generate the final database file. • Should allow the execution of scripts, in order to apply on-the-fly modifications to partitions. • The functionalities implemented should be used to develop higher level functions to support very specific user needs.

  6. Example: //Crating a new LVL2 partition (ROS=8, L2SV=2, L2PU=0). Partition p = new Partition(‘LVL2’,8,2,0); //Scalability test varying the number of L2PUs from 1 to 30. for i=1:30, L2PUApp l2pu = new L2PUApp(); // Creating a new L2PU application. p.addComponents(l2pu); // Adding the new application. p.export(‘my_part.xml’); // Generating the database file. // User made function to test the TDAQ with the generate partition. testTDAQ(‘my_part.xml’); end

  7. Conclusions • The proposed design approach can effectively reduce the time needed to deploy releases. • The integrated non-interactive interface proposed can optimize, and at the same time, ease the partition creation task. • An small prototype for LVL2 is already being developed using these two approaches.

More Related