WEBVTT

00:00.000 --> 00:11.000
Next up is Thomas on research data line which will be for P.C.

00:11.000 --> 00:12.000
Yes, okay.

00:12.000 --> 00:14.000
I hope you understand that.

00:14.000 --> 00:16.000
We're not going to stop.

00:16.000 --> 00:18.000
Okay, so idea for this.

00:18.000 --> 00:20.000
I'm not going to go.

00:20.000 --> 00:22.000
I'm going to go in a search.

00:22.000 --> 00:24.000
I'm 15 years ago.

00:25.000 --> 00:27.000
We had some technical report on that.

00:27.000 --> 00:29.000
And we also did some case.

00:29.000 --> 00:32.000
That was I was in the system for a minute in the letter.

00:32.000 --> 00:34.000
But it was really easy.

00:34.000 --> 00:36.000
I'm going to explain this for you.

00:36.000 --> 00:38.000
And I'm going to show you the structure.

00:38.000 --> 00:39.000
You're going to work on easy.

00:39.000 --> 00:41.000
That you may be using the device.

00:41.000 --> 00:42.000
Please.

00:42.000 --> 00:43.000
We can do this.

00:43.000 --> 00:44.000
So right.

00:44.000 --> 00:45.000
This.

00:45.000 --> 00:46.000
I'm going to go.

00:46.000 --> 00:47.000
So.

00:47.000 --> 00:48.000
So.

00:48.000 --> 00:49.000
So.

00:49.000 --> 00:50.000
So.

00:51.000 --> 01:05.000
So.

01:05.000 --> 01:08.000
So.

01:08.000 --> 01:10.000
So.

01:10.000 --> 01:13.000
So.

01:13.000 --> 01:15.000
So.

01:15.000 --> 01:16.000
So.

01:16.000 --> 01:28.000
But actually the source of you want to have some kind of creative chaos.

01:28.000 --> 01:30.000
I don't know, it's brilliant.

01:30.000 --> 01:34.000
And I can also just tell you what's fun there.

01:34.000 --> 01:36.000
I understand.

01:36.000 --> 01:38.000
Search there.

01:38.000 --> 01:40.000
So, I don't know if there's more products.

01:40.000 --> 01:42.000
So, I don't know if there's more products.

01:42.000 --> 01:44.000
I think this is a sort of management.

01:44.000 --> 01:46.000
It's not really a knowledge from the regulations.

01:46.000 --> 01:50.000
So, if you go out, look at that.

01:50.000 --> 01:52.000
If you're not going to be established,

01:52.000 --> 01:56.000
I don't know, whatever the issues you would be in the post of the professor,

01:56.000 --> 02:00.000
you rarely find anything about the search there.

02:00.000 --> 02:04.000
I would guess it's the same as the whole side of everything you do.

02:04.000 --> 02:06.000
You have to write the statement.

02:06.000 --> 02:12.000
You never really get anything that you understand.

02:12.000 --> 02:16.000
Also, it's very often found at any organization,

02:16.000 --> 02:18.000
because it has some training and some policies,

02:18.000 --> 02:20.000
but not much more than that.

02:20.000 --> 02:22.000
And of course, the post of the professor's time,

02:22.000 --> 02:26.000
to what they do is they really do the many of them

02:26.000 --> 02:32.000
to satisfy the funders' requirements.

02:32.000 --> 02:34.000
But there's actually more products

02:34.000 --> 02:36.000
through the searchers.

02:36.000 --> 02:40.000
So, they have to deal with many different IT systems.

02:40.000 --> 02:42.000
They're all that products.

02:42.000 --> 02:44.000
They may be seeing,

02:44.000 --> 02:46.000
but they use many different search packages.

02:46.000 --> 02:48.000
I hope that if they develop,

02:48.000 --> 02:50.000
or they also have to increase

02:50.000 --> 02:52.000
the rigidity of the architectures.

02:52.000 --> 02:54.000
And then,

02:54.000 --> 02:56.000
Subway or architectures,

02:56.000 --> 03:00.000
so gentlemen, in search of an astronaut today,

03:00.000 --> 03:02.000
they kind of have to manage

03:02.000 --> 03:04.000
with the search of data,

03:04.000 --> 03:06.000
and such that this is no relevant project.

03:06.000 --> 03:08.000
Moving data,

03:08.000 --> 03:10.000
and then also,

03:10.000 --> 03:12.000
by the relevant system,

03:12.000 --> 03:14.000
I can actually see this from there.

03:14.000 --> 03:16.000
Very different storage space,

03:16.000 --> 03:18.000
and from there,

03:18.000 --> 03:20.000
and for this,

03:20.000 --> 03:22.000
it doesn't make any sense.

03:22.000 --> 03:24.000
So, now,

03:24.000 --> 03:26.000
you can do the picture.

03:26.000 --> 03:28.000
So, you can write it,

03:28.000 --> 03:30.000
and then,

03:30.000 --> 03:31.000
or if you know,

03:31.000 --> 03:31.500
there is very much

03:31.500 --> 03:35.000
of many different search packages.

03:35.000 --> 03:37.000
You can just find anything about that,

03:37.000 --> 03:39.000
the $100 much bigger,

03:40.000 --> 03:42.000
and,

03:42.000 --> 03:43.000
that's all,

03:43.000 --> 03:44.000
has all these different license cap.

03:44.000 --> 03:46.000
Because they have to be available online systems,

03:46.000 --> 03:48.000
then also,

03:48.000 --> 03:50.000
but I think,

03:50.000 --> 03:51.000
I'd be the tools,

03:51.000 --> 03:52.000
and actually improves it.

03:52.000 --> 03:53.000
Subway,

03:53.000 --> 03:55.000
because it's available

03:55.000 --> 03:56.000
for the architecture.

03:56.000 --> 03:57.000
But,

03:57.000 --> 03:59.000
the cate andsitu is available

03:59.000 --> 04:05.000
But the question is how can we help with managing these data?

04:09.000 --> 04:13.000
So the question also, if you want to ask,

04:13.000 --> 04:19.000
if you want to examine these data, and then you don't have to limit it in place.

04:19.000 --> 04:25.000
You want to avoid all these other data management operations.

04:25.000 --> 04:33.000
And there's a why you would like to use easier because everyone's already used.

04:33.000 --> 04:37.000
And there's, I think, easy to watch the races.

04:39.000 --> 04:45.000
And the easiest answer is, if you think of it as a free return,

04:45.000 --> 04:49.000
it's for scientific solutions.

04:49.000 --> 04:53.000
And if you don't have to limit it, it's for you to buy it.

04:53.000 --> 04:57.000
If not for new data, or you just put a scientific structure in it.

04:57.000 --> 05:01.000
You want to use it as a free return.

05:01.000 --> 05:03.000
But what are you looking for in this thing?

05:03.000 --> 05:07.000
So you use it on any system.

05:07.000 --> 05:09.000
And that's how it's allowed.

05:09.000 --> 05:13.000
You can use it in the next things.

05:13.000 --> 05:17.000
And you can use it as a free return.

05:17.000 --> 05:21.000
And you also can use it.

05:21.000 --> 05:23.000
So we don't want to do it.

05:23.000 --> 05:25.000
So the problem is that if you use our strength there,

05:25.000 --> 05:29.000
or this system again and again, you know, you want to do it together.

05:29.000 --> 05:31.000
And it's very good for this.

05:31.000 --> 05:37.000
So I'm attempting to use it as a free return service,

05:37.000 --> 05:39.000
or you want to use it as a bit this.

05:39.000 --> 05:43.000
And also, it allows us to collaborate more.

05:43.000 --> 05:45.000
Okay.

05:45.000 --> 05:49.000
So if you use the structure manuals to the left,

05:49.000 --> 05:51.000
actually, if you think that you've seen this before,

05:51.000 --> 05:53.000
so we don't get stuck there,

05:53.000 --> 05:55.000
or they're always stuck there.

05:55.000 --> 05:57.000
So if you don't use it,

05:57.000 --> 05:59.000
and you can use it in the next thing,

05:59.000 --> 06:01.000
then just do not work it.

06:01.000 --> 06:03.000
Sorry.

06:03.000 --> 06:05.000
Okay, now.

06:05.000 --> 06:07.000
Okay, I'm sorry.

06:07.000 --> 06:09.000
And then in the middle,

06:09.000 --> 06:11.000
they have this compatibility.

06:11.000 --> 06:13.000
We use again to for that.

06:13.000 --> 06:15.000
And so that allows us to,

06:15.000 --> 06:17.000
at the top layer,

06:17.000 --> 06:21.000
we don't have to care about all these different Linux distributions.

06:21.000 --> 06:23.000
And here, the file says,

06:23.000 --> 06:24.000
let's say, I want to mention,

06:24.000 --> 06:27.000
is that Javi is shown with us to distribute

06:27.000 --> 06:29.000
the software across the world.

06:29.000 --> 06:31.000
It's a proven solution that scares very well.

06:31.000 --> 06:35.000
And you can get quickly access to it.

06:35.000 --> 06:39.000
So once we add the software package

06:39.000 --> 06:41.000
on our sample server,

06:41.000 --> 06:45.000
it comes with a minute available everywhere.

06:45.000 --> 06:47.000
So that's very convenient.

06:47.000 --> 06:49.000
Okay.

06:49.000 --> 06:55.000
So here's a little bit different way of showing this.

06:55.000 --> 06:59.000
And so of course, we don't want to extend this here in the software there.

06:59.000 --> 07:03.000
Because then you would have to do this in many packages.

07:03.000 --> 07:07.000
It's much better if you do this here in the comfort layer.

07:07.000 --> 07:11.000
So where we have to sort of again to layer.

07:11.000 --> 07:15.000
And so the assumption is that all,

07:15.000 --> 07:17.000
let's say, all that may not all,

07:17.000 --> 07:21.000
but most of the data access goes through the comfort layer.

07:21.000 --> 07:25.000
And then through the file system.

07:25.000 --> 07:27.000
And so we have,

07:27.000 --> 07:31.000
example, open functions,

07:31.000 --> 07:33.000
read, write, close, and so on.

07:33.000 --> 07:35.000
And these are all part of GNIPC.

07:35.000 --> 07:39.000
So if we do something with that,

07:39.000 --> 07:43.000
then change their applied to all the software package.

07:43.000 --> 07:45.000
So how can we change it?

07:45.000 --> 07:47.000
So we could, of course,

07:47.000 --> 07:49.000
because we build GNIPC from source,

07:49.000 --> 07:51.000
we could directly change GNIPC.

07:51.000 --> 07:55.000
So that's more of the advantages

07:55.000 --> 07:57.000
really transparent for you.

07:57.000 --> 07:59.000
And I don't need to change anything.

07:59.000 --> 08:03.000
But also the problem is that it's always on,

08:03.000 --> 08:05.000
whether you want it needed or not.

08:05.000 --> 08:11.000
And they also may have some on the consequences.

08:11.000 --> 08:15.000
And yeah.

08:15.000 --> 08:19.000
You also need to change what you already should

08:19.000 --> 08:20.000
within you.

08:20.000 --> 08:23.000
Yeah, so maybe that's also what you don't want.

08:23.000 --> 08:27.000
And other way could be that you read functions

08:27.000 --> 08:29.000
and then we use the pre-load.

08:29.000 --> 08:33.000
Of course, the advantage of that goes with that.

08:33.000 --> 08:35.000
The key to the full GNIPC.

08:35.000 --> 08:39.000
And it could be easily switched on off by users.

08:39.000 --> 08:43.000
There's advantages we have to sort of adjust

08:43.000 --> 08:45.000
every run process.

08:45.000 --> 08:47.000
So and you kind of make this very transparent.

08:47.000 --> 08:49.000
And yeah.

08:49.000 --> 08:53.000
And of course, it can also again create conflicts.

08:53.000 --> 08:55.000
If you set the slow release,

08:55.000 --> 08:59.000
you would apply to all codes,

08:59.000 --> 09:01.000
we run, maybe they don't.

09:01.000 --> 09:03.000
Maybe they've taken all the codes,

09:03.000 --> 09:05.000
the programs we execute,

09:05.000 --> 09:07.000
that are not part of eerie,

09:07.000 --> 09:09.000
but we're going to come from systems like swear or command.

09:09.000 --> 09:11.000
So yeah.

09:11.000 --> 09:13.000
For prototype,

09:13.000 --> 09:15.000
we do the grabbing of functions

09:15.000 --> 09:17.000
and use the pre-load.

09:17.000 --> 09:21.000
So now some ideas what we could actually

09:21.000 --> 09:23.000
wrap as to what we could do with that.

09:23.000 --> 09:27.000
So we could log information for codes.

09:27.000 --> 09:29.000
And it's like open access.

09:29.000 --> 09:31.000
And then later on once we have a log,

09:31.000 --> 09:35.000
we can post-process that and create data flow grounds.

09:35.000 --> 09:41.000
We could also enable that we use remote data directly.

09:41.000 --> 09:43.000
So we don't have to manually download them,

09:43.000 --> 09:45.000
and then open them,

09:45.000 --> 09:49.000
and use them, but we can directly move them.

09:49.000 --> 09:53.000
And we can also define some kind of virtual data infrastructure.

09:53.000 --> 09:55.000
We just have to say, okay,

09:55.000 --> 09:57.000
so this data will be belongs to this,

09:57.000 --> 09:59.000
what I want to use,

09:59.000 --> 10:01.000
some kind of view over the namespace,

10:01.000 --> 10:03.000
and then some runtime and choose

10:03.000 --> 10:05.000
that the data is there,

10:05.000 --> 10:07.000
as accessible and drawn.

10:09.000 --> 10:11.000
Okay, so now we just want to go

10:11.000 --> 10:15.000
to move it to this idea and show what is needed to do.

10:15.000 --> 10:17.000
It's an example for open.

10:19.000 --> 10:21.000
So if we register,

10:21.000 --> 10:23.000
we can just print something and do a log.

10:23.000 --> 10:27.000
And then we have to call the actual open function.

10:27.000 --> 10:29.000
So it's not so difficult.

10:29.000 --> 10:32.000
The compilation is also not so difficult,

10:32.000 --> 10:34.000
and then to use this,

10:34.000 --> 10:36.000
we can just use any pre-load,

10:36.000 --> 10:38.000
and then, in fact,

10:38.000 --> 10:41.000
some of the cat maybe not very scientifically interesting,

10:41.000 --> 10:43.000
but yeah.

10:43.000 --> 10:47.000
And then what we get is we get some log lines,

10:47.000 --> 10:51.000
and we can have many information in there,

10:51.000 --> 10:53.000
and then basically what then we have,

10:53.000 --> 10:55.000
as we get something like, okay,

10:55.000 --> 10:56.000
there was a program,

10:56.000 --> 10:58.000
it produced some image,

10:58.000 --> 11:01.000
and then maybe this image later,

11:01.000 --> 11:04.000
we used to make a publication.

11:04.000 --> 11:06.000
And then, of course,

11:06.000 --> 11:11.000
we put connect sort of these two,

11:11.000 --> 11:17.000
programs and variety of defines.

11:17.000 --> 11:21.000
Okay, there are many different use cases,

11:21.000 --> 11:23.000
what we can do,

11:23.000 --> 11:25.000
so we can sort of automatically,

11:25.000 --> 11:27.000
then we have the image and the end,

11:27.000 --> 11:30.000
we can start from the data source,

11:30.000 --> 11:33.000
and get a full buffer of what we did.

11:33.000 --> 11:34.000
Yeah.

11:34.000 --> 11:35.000
And of course,

11:35.000 --> 11:36.000
if we do this,

11:36.000 --> 11:37.000
let's say,

11:37.000 --> 11:38.000
not this already,

11:38.000 --> 11:39.000
we have more here,

11:40.000 --> 11:42.000
we can also generate a workflow of that,

11:42.000 --> 11:43.000
and then we can use that,

11:43.000 --> 11:45.000
and copy the workflow,

11:45.000 --> 11:47.000
managements of like,

11:47.000 --> 11:48.000
next close,

11:48.000 --> 11:49.000
make an all this,

11:49.000 --> 11:51.000
and yeah.

11:51.000 --> 11:53.000
Another interesting use case could be that,

11:53.000 --> 11:57.000
maybe if many data files we wanted to analyze,

11:57.000 --> 12:00.000
but we don't know if we actually use them all,

12:00.000 --> 12:04.000
so we could check if we have already used all these data files.

12:04.000 --> 12:05.000
Okay,

12:05.000 --> 12:08.000
so we could also maybe sort of go

12:08.000 --> 12:09.000
with back in time,

12:09.000 --> 12:11.000
because if we do a lot of times them,

12:11.000 --> 12:13.000
we could check what did we do on Monday,

12:13.000 --> 12:14.000
because maybe on Monday,

12:14.000 --> 12:16.000
I had a good idea,

12:16.000 --> 12:17.000
and we learned to check this easily,

12:17.000 --> 12:21.000
and we don't have to lock this manually.

12:21.000 --> 12:23.000
There are some ideas,

12:23.000 --> 12:24.000
when I worked on this,

12:24.000 --> 12:26.000
so it's been the negative sort of spinners,

12:26.000 --> 12:30.000
for filling up the start times of programs,

12:30.000 --> 12:32.000
that need a lot of libraries,

12:32.000 --> 12:34.000
and we could also use it for this,

12:34.000 --> 12:35.000
and of course,

12:35.000 --> 12:38.000
and we also interesting is that we could actually use it also,

12:38.000 --> 12:40.000
for easy itself,

12:40.000 --> 12:41.000
when we build software,

12:41.000 --> 12:43.000
it's very important that we only build

12:43.000 --> 12:46.000
the software that is already in ease,

12:46.000 --> 12:47.000
when the software layer,

12:47.000 --> 12:49.000
or in the compatibility layer,

12:49.000 --> 12:51.000
not elsewhere,

12:51.000 --> 12:53.000
because that could then make problems,

12:53.000 --> 12:54.000
when we ship it,

12:54.000 --> 12:56.000
and maybe the software we use on the build system,

12:56.000 --> 12:58.000
it's not very user.

13:00.000 --> 13:01.000
Okay,

13:01.000 --> 13:02.000
and then of course,

13:02.000 --> 13:04.000
we could also use this to pre-load the cache,

13:04.000 --> 13:06.000
to improve start-up times.

13:07.000 --> 13:10.000
Another idea is sort of to,

13:10.000 --> 13:11.000
in a novel,

13:11.000 --> 13:14.000
access to remote data directly,

13:14.000 --> 13:16.000
so pattern would be usually

13:16.000 --> 13:18.000
that you find something interesting,

13:18.000 --> 13:19.000
you download it,

13:19.000 --> 13:21.000
and then you start using it,

13:21.000 --> 13:23.000
and to go of that would be,

13:23.000 --> 13:24.000
of course,

13:24.000 --> 13:28.000
that you sort of avoid this manual download set.

13:28.000 --> 13:30.000
And as a benefit of that,

13:30.000 --> 13:33.000
it would also be that you make very explicit,

13:33.000 --> 13:35.000
where it's got the data from.

13:35.000 --> 13:36.000
In the work event,

13:36.000 --> 13:39.000
you see the data from,

13:39.000 --> 13:43.000
and the nice thing is also when data is associated with these,

13:43.000 --> 13:45.000
persistent alignifiers,

13:45.000 --> 13:47.000
you can get metadata from the data,

13:47.000 --> 13:52.000
and then enrich the description of the data flow.

13:54.000 --> 13:57.000
So it's just an example of how this could look like,

13:57.000 --> 13:59.000
but again, for open,

13:59.000 --> 14:00.000
we could check,

14:00.000 --> 14:01.000
okay,

14:01.000 --> 14:02.000
it's just a URL.

14:02.000 --> 14:03.000
The person,

14:03.000 --> 14:04.000
you have there,

14:04.000 --> 14:05.000
then download it,

14:05.000 --> 14:06.000
and then,

14:06.000 --> 14:07.000
do the,

14:07.000 --> 14:08.000
the actual open list,

14:08.000 --> 14:10.000
sort of the local copy.

14:10.000 --> 14:11.000
And for the user,

14:11.000 --> 14:14.000
this looks totally transparent.

14:14.000 --> 14:16.000
And so again,

14:16.000 --> 14:17.000
if you compile this,

14:17.000 --> 14:19.000
it's not much more difficult,

14:19.000 --> 14:21.000
and then you sort of,

14:21.000 --> 14:23.000
maybe have some options that you can say,

14:23.000 --> 14:24.000
okay,

14:24.000 --> 14:25.000
so there's some space,

14:25.000 --> 14:27.000
where you can make a copy of this,

14:27.000 --> 14:29.000
and then you have sort of,

14:29.000 --> 14:30.000
now here,

14:30.000 --> 14:31.000
a little command,

14:31.000 --> 14:32.000
you say,

14:32.000 --> 14:33.000
okay,

14:33.000 --> 14:34.000
so it's really ironic,

14:34.000 --> 14:36.000
and then you just understand the command,

14:36.000 --> 14:38.000
and this URL looks very long,

14:38.000 --> 14:39.000
yeah?

14:39.000 --> 14:41.000
And so what we could think of,

14:41.000 --> 14:43.000
is that to improve this a bit,

14:43.000 --> 14:46.000
that we actually specify the UI,

14:46.000 --> 14:48.000
so for them you have to improve a bit,

14:48.000 --> 14:49.000
the implementation,

14:49.000 --> 14:51.000
but this could also work.

14:52.000 --> 14:56.000
Okay, so this actually works surprisingly well,

14:56.000 --> 14:58.000
although not for all commands,

14:58.000 --> 14:59.000
but I tested this,

14:59.000 --> 15:01.000
but how it did work,

15:01.000 --> 15:02.000
and all at the moment,

15:02.000 --> 15:04.000
there were only words for red excess,

15:04.000 --> 15:06.000
but also worked for right.

15:06.000 --> 15:07.000
So for right,

15:07.000 --> 15:10.000
what you would need is some kind of API,

15:10.000 --> 15:12.000
at the back,

15:12.000 --> 15:14.000
and that sort of supports the actual right,

15:14.000 --> 15:16.000
and so,

15:16.000 --> 15:18.000
and you probably would do the upload,

15:18.000 --> 15:20.000
when you file it's close.

15:20.000 --> 15:24.000
Okay,

15:24.000 --> 15:25.000
okay,

15:25.000 --> 15:29.000
maybe I skipped the rest of that,

15:29.000 --> 15:32.000
so then sort of the last idea was that,

15:32.000 --> 15:36.000
you defined some kind of virtual data infrastructure,

15:36.000 --> 15:39.000
and what you could do is that you,

15:39.000 --> 15:42.000
maybe say you define some namespace,

15:42.000 --> 15:43.000
and maybe some labor,

15:43.000 --> 15:46.000
so it identifies that you want to use,

15:47.000 --> 15:51.000
and the search would then only give it a name,

15:51.000 --> 15:55.000
and read just some of these data files,

15:55.000 --> 15:57.000
or maybe even the words,

15:57.000 --> 16:00.000
but the data resides.

16:00.000 --> 16:05.000
And then sometimes runtime would figure out where the files actually stored,

16:05.000 --> 16:06.000
it's already local,

16:06.000 --> 16:08.000
or it says remote,

16:08.000 --> 16:09.000
and it has to be downloaded.

16:09.000 --> 16:10.000
And then,

16:10.000 --> 16:15.000
because many things are all basically based on HTTP,

16:16.000 --> 16:18.000
you know, we can also redirect,

16:18.000 --> 16:21.000
to a different source, different backend.

16:21.000 --> 16:24.000
And we can do much more of that.

16:24.000 --> 16:27.000
And so what we did,

16:27.000 --> 16:29.000
so in the first step,

16:29.000 --> 16:32.000
we created some commands,

16:32.000 --> 16:34.000
they can create some of these namespace,

16:34.000 --> 16:35.000
you can list them,

16:35.000 --> 16:37.000
and you can upload files,

16:37.000 --> 16:40.000
and so there we also sometimes,

16:41.000 --> 16:45.000
we can manage all those,

16:45.000 --> 16:48.000
and then you can get a link,

16:48.000 --> 16:54.000
and to then just sort of back under the link,

16:54.000 --> 16:56.000
and then you can just say head,

16:56.000 --> 16:59.000
and then you see sort of the output of that.

16:59.000 --> 17:03.000
But this really is just basic proof of concept.

17:03.000 --> 17:05.000
To both the status,

17:05.000 --> 17:08.000
we have some prototype implementation.

17:08.000 --> 17:11.000
We have some command line tool,

17:11.000 --> 17:12.000
with the eye,

17:12.000 --> 17:15.000
which you can use to run things,

17:15.000 --> 17:18.000
but also to manipulate this,

17:18.000 --> 17:20.000
virtual data infrastructure,

17:20.000 --> 17:23.000
and to add files to that,

17:23.000 --> 17:24.000
and it's all,

17:24.000 --> 17:26.000
it's open source,

17:26.000 --> 17:27.000
it's a processor,

17:27.000 --> 17:29.000
it's built-in source in less than a minute,

17:29.000 --> 17:30.000
it's very easy,

17:30.000 --> 17:32.000
it could be shipped with easy,

17:32.000 --> 17:33.000
it's not shipped easy,

17:33.000 --> 17:35.000
but could be in principle,

17:35.000 --> 17:39.000
and we have some kind of server infrastructure for front end,

17:39.000 --> 17:40.000
and back end,

17:40.000 --> 17:42.000
so that the author's nice,

17:42.000 --> 17:43.000
is to use it,

17:43.000 --> 17:44.000
if you don't want to use it,

17:44.000 --> 17:46.000
on that.

17:46.000 --> 17:49.000
Okay, so Outlooks of what we could do

17:49.000 --> 17:51.000
is with these data flow graphs,

17:51.000 --> 17:55.000
we could actually export them to tools like next flows,

17:55.000 --> 17:57.000
make, make,

17:57.000 --> 18:00.000
make nice visualizations of this work,

18:00.000 --> 18:02.000
and so that you can create

18:03.000 --> 18:05.000
the picture, the slay tag,

18:05.000 --> 18:07.000
and then you can edit to your publication.

18:07.000 --> 18:09.000
We go, of course,

18:09.000 --> 18:11.000
could intercept more,

18:11.000 --> 18:13.000
more functions,

18:13.000 --> 18:14.000
and yeah,

18:14.000 --> 18:15.000
so what is,

18:15.000 --> 18:17.000
what I learned is the next talk,

18:17.000 --> 18:18.000
we have something,

18:18.000 --> 18:20.000
also both virtual engines,

18:20.000 --> 18:22.000
and they also use irons,

18:22.000 --> 18:24.000
so interfacing this as a back end,

18:24.000 --> 18:25.000
but very good,

18:25.000 --> 18:27.000
because then the problem is a little bit

18:27.000 --> 18:29.000
that how do we access

18:29.000 --> 18:31.000
the data files system,

18:31.000 --> 18:33.000
and the remote system?

18:33.000 --> 18:34.000
Yeah,

18:34.000 --> 18:36.000
and I think this could be,

18:36.000 --> 18:38.000
done very well with this,

18:38.000 --> 18:42.000
what the next speaker will probably tell about.

18:42.000 --> 18:44.000
Okay, summary,

18:44.000 --> 18:46.000
so working with the search,

18:46.000 --> 18:47.000
that is not too easy,

18:47.000 --> 18:48.000
huh?

18:48.000 --> 18:50.000
We have two tools,

18:50.000 --> 18:53.000
a couple of today,

18:53.000 --> 18:57.000
a lot of data to create this data work progress,

18:57.000 --> 18:58.000
and then,

18:58.000 --> 19:02.000
so effortlessly accessing remote data,

19:02.000 --> 19:04.000
we have some prototype,

19:04.000 --> 19:06.000
and so with that,

19:06.000 --> 19:10.000
let's say if this vision becomes fully implemented,

19:10.000 --> 19:11.000
then I think the researchers,

19:11.000 --> 19:14.000
they can focus on working with the data,

19:14.000 --> 19:16.000
and don't have to,

19:16.000 --> 19:19.000
and some tools take care of all the logistics for the data.

19:23.000 --> 19:25.000
Okay, some resources,

19:25.000 --> 19:27.000
if you want to look up more,

19:27.000 --> 19:28.000
the original reporter,

19:28.000 --> 19:30.000
and some case studies,

19:30.000 --> 19:31.000
so of course easy,

19:31.000 --> 19:33.000
if you don't know about easy,

19:33.000 --> 19:34.000
you can look it up,

19:34.000 --> 19:36.000
so if you have a slacker,

19:36.000 --> 19:41.000
you can either join everything in this open source,

19:41.000 --> 19:46.000
or to most of the development of easy data,

19:46.000 --> 19:49.000
funded by your HPC set of excellent,

19:49.000 --> 19:51.000
excellent,

19:51.000 --> 19:52.000
might it exist,

19:52.000 --> 19:54.000
and all the codes for this talk.

19:58.000 --> 19:59.000
Okay, let's go.

20:04.000 --> 20:05.000
Thank you Thomas.

20:05.000 --> 20:07.000
You have plenty for a couple of questions.

20:07.000 --> 20:08.000
Yeah.

20:08.000 --> 20:09.000
Yeah.

20:11.000 --> 20:12.000
For the website,

20:12.000 --> 20:15.000
we're going to go in.

20:16.000 --> 20:19.000
Do you expect it to be feasible

20:19.000 --> 20:21.000
to implement blocking

20:21.000 --> 20:24.000
for remote pilots,

20:24.000 --> 20:26.000
or is that just there,

20:26.000 --> 20:30.000
we can go down and see if you can get the site.

20:30.000 --> 20:32.000
Did you say locking?

20:32.000 --> 20:33.000
Yeah.

20:33.000 --> 20:34.000
Yeah.

20:34.000 --> 20:35.000
So, yeah.

20:35.000 --> 20:36.000
So, if you're right,

20:36.000 --> 20:37.000
you're going to be the question.

20:37.000 --> 20:38.000
Okay, so the question is,

20:38.000 --> 20:41.000
if I expect that we need locking

20:41.000 --> 20:44.000
for providing the multi-day-end.

20:44.000 --> 20:45.000
Right?

20:45.000 --> 20:46.000
Yeah.

20:46.000 --> 20:50.000
So, if there could be multiple vertices,

20:50.000 --> 20:52.000
I think there need to be something.

20:52.000 --> 20:54.000
There need to be some synchronization

20:54.000 --> 20:56.000
among the writers.

21:16.000 --> 21:18.000
I don't fully know.

21:18.000 --> 21:20.000
Okay, so,

21:21.000 --> 21:23.000
the question is,

21:23.000 --> 21:24.000
sort of,

21:24.000 --> 21:26.000
might provide a big coordinate,

21:26.000 --> 21:28.000
since I was right.

21:28.000 --> 21:29.000
Yeah.

21:29.000 --> 21:31.000
I don't know.

21:31.000 --> 21:33.000
I would expect you to need something like this.

21:33.000 --> 21:35.000
So, there was some work,

21:35.000 --> 21:38.000
like maybe 25 years ago

21:38.000 --> 21:43.000
on implementing sort of kind of virtual

21:43.000 --> 21:45.000
this is a child's memory.

21:45.000 --> 21:48.000
And so, there was a development

21:48.000 --> 21:51.000
of different ways to synchronize

21:51.000 --> 21:53.000
with different consistency models

21:53.000 --> 21:54.000
and maybe,

21:54.000 --> 21:56.000
I could look into this to see

21:56.000 --> 21:57.000
if there are supposed to be

21:57.000 --> 21:58.000
questions,

21:58.000 --> 22:01.000
how to implement this efficiently.

22:01.000 --> 22:02.000
Yeah.

22:02.000 --> 22:03.000
And, yeah.

22:03.000 --> 22:04.000
Thank you.

22:04.000 --> 22:05.000
Thank you.

22:05.000 --> 22:06.000
Thank you.

22:06.000 --> 22:08.000
More questions?

22:12.000 --> 22:13.000
I have one, maybe, two,

22:13.000 --> 22:14.000
one.

22:14.000 --> 22:16.000
Why are anyone 12 this year?

22:16.000 --> 22:17.000
Maybe.

22:17.000 --> 22:18.000
It's a stupid idea.

22:18.000 --> 22:19.000
I don't know.

22:19.000 --> 22:21.000
It seems like a simple concept.

22:21.000 --> 22:22.000
I don't know.

22:22.000 --> 22:23.000
So,

22:27.000 --> 22:29.000
Does anyone have an answer?

22:29.000 --> 22:30.000
Yes.

22:30.000 --> 22:31.000
I don't have an answer.

22:31.000 --> 22:33.000
Also, there is no question.

22:33.000 --> 22:35.000
Because, I might be the only person

22:35.000 --> 22:36.000
to see that.

22:36.000 --> 22:38.000
So, you can also think about

22:38.000 --> 22:39.000
about this.

22:39.000 --> 22:41.000
There is a lot of experience

22:41.000 --> 22:42.000
for this could end up in

22:42.000 --> 22:43.000
something like that.

22:43.000 --> 22:44.000
I don't know.

22:45.000 --> 22:47.000
So, the question is,

22:47.000 --> 22:49.000
is all the data that is lost?

22:49.000 --> 22:51.000
Those into some kind of

22:51.000 --> 22:52.000
lots books,

22:52.000 --> 22:53.000
some notebooks,

22:53.000 --> 22:55.000
so the way it would keep

22:55.000 --> 22:57.000
normally nodes in the lab.

22:57.000 --> 22:58.000
Oh, yes.

22:58.000 --> 23:00.000
You could do this.

23:00.000 --> 23:01.000
So, actually,

23:01.000 --> 23:03.000
I would think that maybe,

23:03.000 --> 23:05.000
if you just want to focus on the fun.

23:05.000 --> 23:06.000
Yeah,

23:06.000 --> 23:09.000
not on all this logging and keeping nodes.

23:09.000 --> 23:11.000
One could use it.

23:12.000 --> 23:15.000
So, I think that we can prove

23:15.000 --> 23:18.000
something like this with

23:18.000 --> 23:21.000
I,

23:21.000 --> 23:24.000
such as post-expression systems,

23:24.000 --> 23:27.000
and we can probably use the metadata.

23:27.000 --> 23:28.000
I also do,

23:28.000 --> 23:29.000
like,

23:29.000 --> 23:30.000
three of the logs.

23:30.000 --> 23:31.000
So, in data,

23:31.000 --> 23:32.000
two,

23:32.000 --> 23:33.000
because the metadata,

23:33.000 --> 23:34.000
I actually have the device

23:34.000 --> 23:35.000
for the database.

23:35.000 --> 23:36.000
Yeah.

23:36.000 --> 23:37.000
So,

23:37.000 --> 23:39.000
I think that is the way to do that.

23:39.000 --> 23:40.000
You have to think the comment.

23:40.000 --> 23:41.000
Okay.

23:41.000 --> 23:43.000
So, the comment is that

23:43.000 --> 23:44.000
one could probably use

23:44.000 --> 23:45.000
irots,

23:45.000 --> 23:47.000
because sort of they have

23:47.000 --> 23:48.000
stored information

23:48.000 --> 23:49.000
in some database,

23:49.000 --> 23:50.000
and then,

23:50.000 --> 23:51.000
so,

23:51.000 --> 23:53.000
maybe,

23:53.000 --> 23:55.000
can watch the objects

23:55.000 --> 23:56.000
that are,

23:56.000 --> 23:57.000
sort of.

23:57.000 --> 23:58.000
Yeah.

23:58.000 --> 23:59.000
Okay.

23:59.000 --> 24:01.000
Okay.

24:01.000 --> 24:02.000
Okay.

24:02.000 --> 24:03.000
Okay.

24:03.000 --> 24:04.000
Okay.

24:04.000 --> 24:05.000
So, irots,

24:05.000 --> 24:06.000
do not have to look

24:06.000 --> 24:08.020
Perfectly

24:08.020 --> 24:10.020
from my archives.

24:10.020 --> 24:11.020
Yes.

24:11.020 --> 24:12.020
You are.

24:12.020 --> 24:14.340
There's a story.

24:14.340 --> 24:16.000
Yeah, it's a beat,

24:16.000 --> 24:18.000
or something like that.

24:18.000 --> 24:20.000
It's an ATM.

24:20.000 --> 24:22.040
It's an AAKCANGIS.

24:22.040 --> 24:24.040
It's an AAKCANGIS?

24:24.040 --> 24:25.980
It's an AAKCANGIS.

24:25.980 --> 24:27.000
But it can be recognizing

24:27.000 --> 24:32.140
that it's an ant

24:32.140 --> 24:32.760
And that marijuana is

24:32.760 --> 24:35.000
located in the campus.

24:35.000 --> 24:38.000
Can I do this to you, how is your work?

24:38.000 --> 24:40.000
And if you actually start pulling in,

24:40.000 --> 24:42.000
let's say, to identify the data, why?

24:42.000 --> 24:44.000
Oh, not in the home court.

24:44.000 --> 24:46.000
To the center.

24:46.000 --> 24:47.000
And you're well in the way.

24:47.000 --> 24:49.000
It's got to take a while.

24:49.000 --> 24:50.000
Yeah.

24:50.000 --> 24:51.000
OK.

24:51.000 --> 24:53.000
So some...

24:53.000 --> 24:57.000
So the idea could be that if you use irons and back end,

24:57.000 --> 25:00.000
you just could complain that it's of work,

25:00.000 --> 25:03.000
or so you have to bring it in and get out of the out.

25:03.000 --> 25:05.000
So if you have a layer on top of that,

25:05.000 --> 25:08.000
that sort of makes the transparent that you don't have to do this,

25:08.000 --> 25:10.000
it just works like this normal program,

25:10.000 --> 25:14.000
that this helps in using irons.

25:14.000 --> 25:18.000
But then, OK, the problem is maybe if you have a large address,

25:18.000 --> 25:20.000
that's how to handle this.

25:20.000 --> 25:22.000
And if you do, would do this then,

25:22.000 --> 25:25.000
with the open call, that could be maybe not a best call.

25:25.000 --> 25:29.000
But if you put out maybe with just a week call,

25:29.000 --> 25:33.000
and just say, OK, if they know that the data is in irons,

25:33.000 --> 25:36.000
in the database, you can access it.

25:36.000 --> 25:42.000
You can maybe just use the week call, and all of right doors.

25:42.000 --> 25:45.000
Final job.

25:45.000 --> 25:47.000
Just to come and see you mentioned,

25:47.000 --> 25:50.000
you asked for a few other similar efforts.

25:50.000 --> 25:52.000
I believe there's an important statement,

25:52.000 --> 25:53.000
just for people that need this.

25:53.000 --> 25:55.000
Something from the system,

25:55.000 --> 25:58.000
or bring the platform for analysis.

25:58.000 --> 26:04.000
I don't want the state to order out of the team.

26:04.000 --> 26:06.000
That's from the TSCS.

26:06.000 --> 26:10.000
There's no sweet state to say this data sends it out.

26:10.000 --> 26:13.000
OK, what's the name of the rainbow?

26:13.000 --> 26:14.000
One of each of it.

26:14.000 --> 26:15.000
OK.

26:15.000 --> 26:16.000
What does it mean?

26:16.000 --> 26:17.000
OK.

26:17.000 --> 26:19.000
It gives you beer.

26:19.000 --> 26:20.000
OK.

26:20.000 --> 26:21.000
All right.

26:21.000 --> 26:22.000
Yeah.

26:22.000 --> 26:23.000
Just wrap up.

26:23.000 --> 26:24.000
Thank you.

26:24.000 --> 26:27.000
Thank you.