LAE

Welcome to the LAE community!  Please feel free to start a discussion in the discussion tab or join in a conversation.

Discussions

Members

Resources

Events

 View Only
  • 1.  Best way to retrofit nodes/script across graphs

    Employee
    Posted 04-23-2013 01:52

    Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.

    Originally posted by: snbkumar

    Hi Team,

    Since we are undergoing parallel development in the lavastorm BRGs, we have checkpoints at which we need to retrofit nodes/scripts across BRGs and cannot always rely on developers to exactly specify the nodes they changed/added.

    We tried to come up with an approach to retrofit code across graphs by comparing the BRG as text files. But it seems inefficient.

    Can someone please let me know an approach that works best?

    Thanks,
    Bharath


  • 2.  RE: Best way to retrofit nodes/script across graphs

    Employee
    Posted 04-29-2013 10:41

    Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.

    Originally posted by: rboccuzzi

    There are a number of decent merge tools that you could use, such as this free tool P4 Merge, if you are just using an editor (it wasn't clear from your comment). The format itself is text and can be merged using these standard tools, but we recognize it is not ideal, and will, at some point in the future, be changing the format of the .brg for a few reasons, and this is one we will be attempting to help address as well. I have also logged a request (PR 2206) for implementing a .brg comparison tool that would graphically compare two graphs.

    Cheers
    Rich


  • 3.  RE: Best way to retrofit nodes/script across graphs

    Employee
    Posted 04-29-2013 18:46

    Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.

    Originally posted by: snbkumar

    Thanks a lot Rich.
    1. Yes! When I mentioned "comparing the BRG as text files", I referred to text editor comparison tools.
    2. Is there a way for us to track PR 2206?

    3. Is there a provision to format brainscript/nodes in a graph? To be more clear, I am looking for a way to save a xml (with defined formatting options) and attach to BRG. Click of a button should format all nodes to defined format.
    By formatting options, I refer to below (to name a few):
    i) Indentation of brainscript
    ii) Variable nomenclature
    iii) Node Link in straight lines
    iv) Show nodes having in/out IO with default names instead of meaningful names.

    I would be glad to assist in the creation of this formatting module if you can guide me with a process.

    Thanks,
    Bharath


  • 4.  RE: Best way to retrofit nodes/script across graphs

    Employee
    Posted 04-30-2013 11:41

    Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.

    Originally posted by: rboccuzzi

    Bharath, when a PR is fixed in a release, the PR is noted in the release notes, so you can definitely check to see if it has been fixed in releases as they come out. In general, for our enterprise customers, we provide a support and sales contact that can provide more detailed status and allow you a communication channel to escalate and help prioritize those requests. For our desktop customers, we do have the support email, but generally this is the medium for your voice on this sort of thing. I have noted to Product Management your request and that elevates its priority accordingly.

    There is not a way to format BRAINscript or graphs in any automated way, currently. We do provide the ability to use external editors from the node editor, so you could create macros and language formatting in an editor of your choosing if you like. As we change the format of the .brg in the future to something like XML (potentially), there will be a greater ability to create tools that can autoformat an entire graph in an easier manner.

    Cheers
    Rich


  • 5.  RE: Best way to retrofit nodes/script across graphs

    Employee
    Posted 04-30-2013 23:15

    Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.

    Originally posted by: snbkumar

    Hi Rich,

    Thanks again. Good to know that we might migrate to XML in the future. Is there a reason and a timeline for the migration?

    Regards,
    Bharath


  • 6.  RE: Best way to retrofit nodes/script across graphs

    Employee
    Posted 05-01-2013 11:59

    Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.

    Originally posted by: rboccuzzi

    There isn't an immediate timeline, but probably over the next year or two; the above is one of the reasons for doing it; another is to use a more common standard format, and generally to enable future product enhancements easier.

    Cheers
    Rich


  • 7.  RE: Best way to retrofit nodes/script across graphs

    Employee
    Posted 06-17-2013 04:46

    Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.

    Originally posted by: snbkumar

    Hi Rich,

    Can you please update me on the status of PR 2206?

    Regards, Bharath


  • 8.  RE: Best way to retrofit nodes/script across graphs

    Employee
    Posted 06-19-2013 06:24

    Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.

    Originally posted by: rboccuzzi

    Bharath, this feature is still on our road map, but it has not been assigned to any immediate release. Therefor, the state is still "probably sometime over the next year or two". We are discussing possibly changing the format of the brg in one of the upcoming releases being discussed, which, while not strictly required for this feature, has been a consideration as a potential pre-step.

    Cheers
    Rich