Hi Don,
My previous reply conflated a number of different issues. Yes it is possible to import the accelerators.brg as you describe. When the library paths have been changed, importing a graph that contains accelerator node will resolve the nodes so the subsequent import of the graph will be successful.
However, the nodes in the accelerators.brg are not supported for use with Data3Sixty Analyze.Most of the accelerator nodes are relatively simple in construction - either based on a single node or on a Composite node that contains nodes from the core or lal libraries, and the nodes may well run successfully and operate correctly - though your mileage may vary as the nodes have not been tested in Data3Sixty Analyze. Some node may not work when the graph is imported e.g. here is an example where the Outlier Detection accelerator node generates an error when opened in Data3Sixty Analyze but runs successfully in Lavastorm:
Hence we recommend you replace the accelerator nodes prior to importing the graphs into Data3Sixty Analyze. If required, you can choose to import the legacy library and the graph as-is and then modify them to use supported nodes, but if you want to continue using any of the unsupported accelerator nodes in your data flows you should confirm that they provide the expected results.
Regards,
Adrian