Privacy · Feyn

by: Kevin Broløs
(Feyn version 2.0 or newer)

Privacy is key to us here at Abzu. For that reason, we only send information to the QLattice that is needed for it to deliver better models to you, and only when you explicitly ask Feyn to (or use auto_run).

The information sent to the QLattice when you update therefore only consists of:

The token and QLattice identifiers when you connect.
The names of your features (text strings)
The model structures you want to reinforce, containing: feature names, function names, edges in the graph that connect inputs to functions, functions to functions and functions to outputs.

None of your data is at any point exchanged and does not leave your machine.

What exactly gets sent to the QLattice

Here's a concrete example of models trained using auto_run.

Each epoch of auto_run calls two functions under the hood that communicate with the QLattice:

QLattice.update, where it takes the best models, converts them to a JSON payload and sends it to the QLattice.
QLattice.sample_models, where you provide feature names and the type of model you want to sample.

(notice that auto_run is a method on the QLattice object to denote that it has remote connection).

import feyn

train, test = feyn.datasets.make_classification()

ql = feyn.connect_qlattice()
best_models = ql.auto_run(train, 'y', kind='classification', max_complexity=3)

best_models[0]

In the manual workflow, it's more clear where the connection points with the QLattice happen:

    import feyn
    ql = feyn.connect_qlattice()

    # Connection happens here to sample models from column names
    models = ql.sample_models(train.columns, output_name='y', kind = 'classification', max_complexity=3)

    # This is all performed locally
    models = feyn.fit_models(models, train, criterion='bic')
    models = feyn.prune_models(models)
    best = feyn.best_diverse_models(models)

    # Connection happens here to update the QLattice
    ql.update(best)

The ql.update function takes each model in the list, converts it to json, and sends the resulting model structures to the QLattice in this format (only the first model is displayed here):

    {
        'directed': True,
        'multigraph': True,
        'nodes': [
            {'id': 0,
            'spec': 'in:linear(f)->i',
            'location': (23, -1, -1),
            'peerlocation': (23, -1, -1),
            'legs': 0,
            'strength': 1.0,
            'name': 'x2'},
            {'id': 1,
            'spec': 'in:linear(f)->i',
            'location': (40, -1, -1),
            'peerlocation': (40, -1, -1),
            'legs': 0,
            'strength': 1.0,
            'name': 'x19'},
            {'id': 2,
            'spec': 'cell:gaussian(i,i)->i',
            'location': (17, 6, 4),
            'peerlocation': (17, 6, 4),
            'legs': 2,
            'strength': 1.0,
            'name': ''},
            {'id': 3,
            'spec': 'out:linear(i)->f',
            'location': (18, 5, 4),
            'peerlocation': (18, 5, 4),
            'legs': 1,
            'strength': 1.0,
            'name': 'y'}
        ],
        'links': [
            {'source': 1, 'target': 2, 'ord': 0},
            {'source': 0, 'target': 2, 'ord': 1},
            {'source': 2, 'target': 3, 'ord': 0}
        ]
    }