Section: Mapping { Group: MappingOptions { smethod = "Diffu"; dmethod = "0"; } Group: TaskGraph { ntask = 7; task_name = "master", "sl1", "sl2", "sl3", "sl4", "sl5", "sl6"; fixed = 0; load = 2, 1, 1, 1, 1, 1, 1; nchan = 14; tcomm = 0,1,1, 0,2,1, 0,3,1, 0,4,1, 0,5,1, 0,6,1, 1,0,1, 2,0,1, 3,0,1, 4,0,1, 5,0,1, 6,0,1; } Group: ProcessorGraph { nproc = 4; proc_name = "ups", "savba", "sierra", "sfinx"; speed = 400, 150, 350, 950; pcomm = 100, 400, 100, 1200, 500, 300, 400, 500, 300, 400, 100, 600, 700, 800, 700, 100; } }Here is more info about mapping tool options.
We need to know the task structure, i.e. task graph. In our proposal there can be
We also need to know the hardware structure, i.e. processor graph. There can be in this group
The output that mapping tool creates can be written in the StaticResult group as follows:
Section: Mapping { Group: StaticResult { location = 0, 1, 2, 3, 1, 2, 3; imbalance = 1.34; comm_cost = 254; method = "Diffu"; } }I propose to use third possibility of "how return mapping results to the application" - direct to the compiled "a.out" binary as external data file, i.e. application need not be recompiled (grapnel nor cc). This external file can have the following looks:
Comments send, please, to me or to mapping_format_interesting_people_mailing_list.