Daniil Shunkevich
Daniil Shunkevich
When several agents work with the same sc-element, a deadlock is likely to occur Possibly the problem (or one of them) is somewhere in sc_iterator...._next functions https://github.com/ostis-dev/sc-machine/blob/master/sc-memory/sc-core/sc-store/sc_iterator3.c
sc_result test_agents_func(const sc_event *event, sc_addr arg) { printf("AGENT\n"); sc_memory_context *ctx = sc_memory_context_new(sc_access_lvl_make_min); sc_addr begin; sc_memory_get_arc_begin(ctx, arg, &begin); sc_iterator3* it = sc_iterator3_f_a_a_new(ctx, begin, sc_type_arc_pos_const_perm, sc_type_const); while (sc_iterator3_next(it)) { printf("ARC: %u|%u\n", sc_iterator3_value(it,...
Approximate description of the problem: There is an element that belongs to several sets The first agent iterates over the sets and does some additional checking (does not delete anything)...
Rename basic type classes for SCs sources in sc-builder in accordance with table in document: https://docs.google.com/document/d/1nW18hnETmqBRCvyUq6JywVLkVxx-MU3W4uZf143K3JI/edit Use current system ID's from IMS (are given in second column in table).
Change action classes in accordance with document (see identifiers table): https://docs.google.com/document/d/1uAeOyXOKsT4DGjuCmG8JuTakz13LyXvXuBwsg_blA8E/edit For now use current identifiers from IMS with "question_" prefix.
 При поиске по такому образцу в ответ попадает еще и пятерка Obj4=>nrel_rel_1:Obj2, хотя не должна
* [x] Добавить возможность просмотра всех пар соответствия, полученных в конкретном результате поиска, не зная их общего числа * [ ] Добавить возможность получения результата поиска не по имени элемента,...
ScAddr addr1, addr2; ScTemplateGenParams params; params.add(addr1, addr2);