Next up is Thomas on research data line which will be for P.C.
Yes, okay.
I hope you understand that.
We're not going to stop.
Okay, so idea for this.
I'm not going to go.
I'm going to go in a search.
I'm 15 years ago.
We had some technical report on that.
And we also did some case.
That was I was in the system for a minute in the letter.
But it was really easy.
I'm going to explain this for you.
And I'm going to show you the structure.
You're going to work on easy.
That you may be using the device.
Please.
We can do this.
So right.
This.
I'm going to go.
So.
But actually the source of you want to have some kind of creative chaos.
I don't know, it's brilliant.
And I can also just tell you what's fun there.
I understand.
Search there.
So, I don't know if there's more products.
I think this is a sort of management.
It's not really a knowledge from the regulations.
So, if you go out, look at that.
If you're not going to be established,
I don't know, whatever the issues you would be in the post of the professor,
you rarely find anything about the search there.
I would guess it's the same as the whole side of everything you do.
You have to write the statement.
You never really get anything that you understand.
Also, it's very often found at any organization,
because it has some training and some policies,
but not much more than that.
And of course, the post of the professor's time,
to what they do is they really do the many of them
to satisfy the funders' requirements.
But there's actually more products
through the searchers.
So, they have to deal with many different IT systems.
They're all that products.
They may be seeing,
but they use many different search packages.
I hope that if they develop,
or they also have to increase
the rigidity of the architectures.
And then,
Subway or architectures,
so gentlemen, in search of an astronaut today,
they kind of have to manage
with the search of data,
and such that this is no relevant project.
Moving data,
and then also,
by the relevant system,
I can actually see this from there.
Very different storage space,
and from there,
and for this,
it doesn't make any sense.
So, now,
you can do the picture.
So, you can write it,
and then,
or if you know,
there is very much
of many different search packages.
You can just find anything about that,
the $100 much bigger,
and,
that's all,
has all these different license cap.
Because they have to be available online systems,
then also,
but I think,
I'd be the tools,
and actually improves it.
Subway,
because it's available
for the architecture.
But,
the cate andsitu is available
But the question is how can we help with managing these data?
So the question also, if you want to ask,
if you want to examine these data, and then you don't have to limit it in place.
You want to avoid all these other data management operations.
And there's a why you would like to use easier because everyone's already used.
And there's, I think, easy to watch the races.
And the easiest answer is, if you think of it as a free return,
it's for scientific solutions.
And if you don't have to limit it, it's for you to buy it.
If not for new data, or you just put a scientific structure in it.
You want to use it as a free return.
But what are you looking for in this thing?
So you use it on any system.
And that's how it's allowed.
You can use it in the next things.
And you can use it as a free return.
And you also can use it.
So we don't want to do it.
So the problem is that if you use our strength there,
or this system again and again, you know, you want to do it together.
And it's very good for this.
So I'm attempting to use it as a free return service,
or you want to use it as a bit this.
And also, it allows us to collaborate more.
Okay.
So if you use the structure manuals to the left,
actually, if you think that you've seen this before,
so we don't get stuck there,
or they're always stuck there.
So if you don't use it,
and you can use it in the next thing,
then just do not work it.
Sorry.
Okay, now.
Okay, I'm sorry.
And then in the middle,
they have this compatibility.
We use again to for that.
And so that allows us to,
at the top layer,
we don't have to care about all these different Linux distributions.
And here, the file says,
let's say, I want to mention,
is that Javi is shown with us to distribute
the software across the world.
It's a proven solution that scares very well.
And you can get quickly access to it.
So once we add the software package
on our sample server,
it comes with a minute available everywhere.
So that's very convenient.
Okay.
So here's a little bit different way of showing this.
And so of course, we don't want to extend this here in the software there.
Because then you would have to do this in many packages.
It's much better if you do this here in the comfort layer.
So where we have to sort of again to layer.
And so the assumption is that all,
let's say, all that may not all,
but most of the data access goes through the comfort layer.
And then through the file system.
And so we have,
example, open functions,
read, write, close, and so on.
And these are all part of GNIPC.
So if we do something with that,
then change their applied to all the software package.
So how can we change it?
So we could, of course,
because we build GNIPC from source,
we could directly change GNIPC.
So that's more of the advantages
really transparent for you.
And I don't need to change anything.
But also the problem is that it's always on,
whether you want it needed or not.
And they also may have some on the consequences.
And yeah.
You also need to change what you already should
within you.
Yeah, so maybe that's also what you don't want.
And other way could be that you read functions
and then we use the pre-load.
Of course, the advantage of that goes with that.
The key to the full GNIPC.
And it could be easily switched on off by users.
There's advantages we have to sort of adjust
every run process.
So and you kind of make this very transparent.
And yeah.
And of course, it can also again create conflicts.
If you set the slow release,
you would apply to all codes,
we run, maybe they don't.
Maybe they've taken all the codes,
the programs we execute,
that are not part of eerie,
but we're going to come from systems like swear or command.
So yeah.
For prototype,
we do the grabbing of functions
and use the pre-load.
So now some ideas what we could actually
wrap as to what we could do with that.
So we could log information for codes.
And it's like open access.
And then later on once we have a log,
we can post-process that and create data flow grounds.
We could also enable that we use remote data directly.
So we don't have to manually download them,
and then open them,
and use them, but we can directly move them.
And we can also define some kind of virtual data infrastructure.
We just have to say, okay,
so this data will be belongs to this,
what I want to use,
some kind of view over the namespace,
and then some runtime and choose
that the data is there,
as accessible and drawn.
Okay, so now we just want to go
to move it to this idea and show what is needed to do.
It's an example for open.
So if we register,
we can just print something and do a log.
And then we have to call the actual open function.
So it's not so difficult.
The compilation is also not so difficult,
and then to use this,
we can just use any pre-load,
and then, in fact,
some of the cat maybe not very scientifically interesting,
but yeah.
And then what we get is we get some log lines,
and we can have many information in there,
and then basically what then we have,
as we get something like, okay,
there was a program,
it produced some image,
and then maybe this image later,
we used to make a publication.
And then, of course,
we put connect sort of these two,
programs and variety of defines.
Okay, there are many different use cases,
what we can do,
so we can sort of automatically,
then we have the image and the end,
we can start from the data source,
and get a full buffer of what we did.
Yeah.
And of course,
if we do this,
let's say,
not this already,
we have more here,
we can also generate a workflow of that,
and then we can use that,
and copy the workflow,
managements of like,
next close,
make an all this,
and yeah.
Another interesting use case could be that,
maybe if many data files we wanted to analyze,
but we don't know if we actually use them all,
so we could check if we have already used all these data files.
Okay,
so we could also maybe sort of go
with back in time,
because if we do a lot of times them,
we could check what did we do on Monday,
because maybe on Monday,
I had a good idea,
and we learned to check this easily,
and we don't have to lock this manually.
There are some ideas,
when I worked on this,
so it's been the negative sort of spinners,
for filling up the start times of programs,
that need a lot of libraries,
and we could also use it for this,
and of course,
and we also interesting is that we could actually use it also,
for easy itself,
when we build software,
it's very important that we only build
the software that is already in ease,
when the software layer,
or in the compatibility layer,
not elsewhere,
because that could then make problems,
when we ship it,
and maybe the software we use on the build system,
it's not very user.
Okay,
and then of course,
we could also use this to pre-load the cache,
to improve start-up times.
Another idea is sort of to,
in a novel,
access to remote data directly,
so pattern would be usually
that you find something interesting,
you download it,
and then you start using it,
and to go of that would be,
of course,
that you sort of avoid this manual download set.
And as a benefit of that,
it would also be that you make very explicit,
where it's got the data from.
In the work event,
you see the data from,
and the nice thing is also when data is associated with these,
persistent alignifiers,
you can get metadata from the data,
and then enrich the description of the data flow.
So it's just an example of how this could look like,
but again, for open,
we could check,
okay,
it's just a URL.
The person,
you have there,
then download it,
and then,
do the,
the actual open list,
sort of the local copy.
And for the user,
this looks totally transparent.
And so again,
if you compile this,
it's not much more difficult,
and then you sort of,
maybe have some options that you can say,
okay,
so there's some space,
where you can make a copy of this,
and then you have sort of,
now here,
a little command,
you say,
okay,
so it's really ironic,
and then you just understand the command,
and this URL looks very long,
yeah?
And so what we could think of,
is that to improve this a bit,
that we actually specify the UI,
so for them you have to improve a bit,
the implementation,
but this could also work.
Okay, so this actually works surprisingly well,
although not for all commands,
but I tested this,
but how it did work,
and all at the moment,
there were only words for red excess,
but also worked for right.
So for right,
what you would need is some kind of API,
at the back,
and that sort of supports the actual right,
and so,
and you probably would do the upload,
when you file it's close.
Okay,
okay,
maybe I skipped the rest of that,
so then sort of the last idea was that,
you defined some kind of virtual data infrastructure,
and what you could do is that you,
maybe say you define some namespace,
and maybe some labor,
so it identifies that you want to use,
and the search would then only give it a name,
and read just some of these data files,
or maybe even the words,
but the data resides.
And then sometimes runtime would figure out where the files actually stored,
it's already local,
or it says remote,
and it has to be downloaded.
And then,
because many things are all basically based on HTTP,
you know, we can also redirect,
to a different source, different backend.
And we can do much more of that.
And so what we did,
so in the first step,
we created some commands,
they can create some of these namespace,
you can list them,
and you can upload files,
and so there we also sometimes,
we can manage all those,
and then you can get a link,
and to then just sort of back under the link,
and then you can just say head,
and then you see sort of the output of that.
But this really is just basic proof of concept.
To both the status,
we have some prototype implementation.
We have some command line tool,
with the eye,
which you can use to run things,
but also to manipulate this,
virtual data infrastructure,
and to add files to that,
and it's all,
it's open source,
it's a processor,
it's built-in source in less than a minute,
it's very easy,
it could be shipped with easy,
it's not shipped easy,
but could be in principle,
and we have some kind of server infrastructure for front end,
and back end,
so that the author's nice,
is to use it,
if you don't want to use it,
on that.
Okay, so Outlooks of what we could do
is with these data flow graphs,
we could actually export them to tools like next flows,
make, make,
make nice visualizations of this work,
and so that you can create
the picture, the slay tag,
and then you can edit to your publication.
We go, of course,
could intercept more,
more functions,
and yeah,
so what is,
what I learned is the next talk,
we have something,
also both virtual engines,
and they also use irons,
so interfacing this as a back end,
but very good,
because then the problem is a little bit
that how do we access
the data files system,
and the remote system?
Yeah,
and I think this could be,
done very well with this,
what the next speaker will probably tell about.
Okay, summary,
so working with the search,
that is not too easy,
huh?
We have two tools,
a couple of today,
a lot of data to create this data work progress,
and then,
so effortlessly accessing remote data,
we have some prototype,
and so with that,
let's say if this vision becomes fully implemented,
then I think the researchers,
they can focus on working with the data,
and don't have to,
and some tools take care of all the logistics for the data.
Okay, some resources,
if you want to look up more,
the original reporter,
and some case studies,
so of course easy,
if you don't know about easy,
you can look it up,
so if you have a slacker,
you can either join everything in this open source,
or to most of the development of easy data,
funded by your HPC set of excellent,
excellent,
might it exist,
and all the codes for this talk.
Okay, let's go.
Thank you Thomas.
You have plenty for a couple of questions.
Yeah.
For the website,
we're going to go in.
Do you expect it to be feasible
to implement blocking
for remote pilots,
or is that just there,
we can go down and see if you can get the site.
Did you say locking?
Yeah.
So, yeah.
So, if you're right,
you're going to be the question.
Okay, so the question is,
if I expect that we need locking
for providing the multi-day-end.
Right?
Yeah.
So, if there could be multiple vertices,
I think there need to be something.
There need to be some synchronization
among the writers.
I don't fully know.
Okay, so,
the question is,
sort of,
might provide a big coordinate,
since I was right.
Yeah.
I don't know.
I would expect you to need something like this.
So, there was some work,
like maybe 25 years ago
on implementing sort of kind of virtual
this is a child's memory.
And so, there was a development
of different ways to synchronize
with different consistency models
and maybe,
I could look into this to see
if there are supposed to be
questions,
how to implement this efficiently.
Yeah.
And, yeah.
Thank you.
More questions?
I have one, maybe, two,
one.
Why are anyone 12 this year?
Maybe.
It's a stupid idea.
I don't know.
It seems like a simple concept.
I don't know.
So,
Does anyone have an answer?
Yes.
I don't have an answer.
Also, there is no question.
Because, I might be the only person
to see that.
So, you can also think about
about this.
There is a lot of experience
for this could end up in
something like that.
I don't know.
So, the question is,
is all the data that is lost?
Those into some kind of
lots books,
some notebooks,
so the way it would keep
normally nodes in the lab.
Oh, yes.
You could do this.
So, actually,
I would think that maybe,
if you just want to focus on the fun.
Yeah,
not on all this logging and keeping nodes.
One could use it.
So, I think that we can prove
something like this with
I,
such as post-expression systems,
and we can probably use the metadata.
I also do,
like,
three of the logs.
So, in data,
two,
because the metadata,
I actually have the device
for the database.
Yeah.
So,
I think that is the way to do that.
You have to think the comment.
Okay.
So, the comment is that
one could probably use
irots,
because sort of they have
stored information
in some database,
and then,
so,
maybe,
can watch the objects
that are,
sort of.
Yeah.
Okay.
So, irots,
do not have to look
Perfectly
from my archives.
Yes.
You are.
There's a story.
Yeah, it's a beat,
or something like that.
It's an ATM.
It's an AAKCANGIS.
It's an AAKCANGIS?
It's an AAKCANGIS.
But it can be recognizing
that it's an ant
And that marijuana is
located in the campus.
Can I do this to you, how is your work?
And if you actually start pulling in,
let's say, to identify the data, why?
Oh, not in the home court.
To the center.
And you're well in the way.
It's got to take a while.
Yeah.
OK.
So some...
So the idea could be that if you use irons and back end,
you just could complain that it's of work,
or so you have to bring it in and get out of the out.
So if you have a layer on top of that,
that sort of makes the transparent that you don't have to do this,
it just works like this normal program,
that this helps in using irons.
But then, OK, the problem is maybe if you have a large address,
that's how to handle this.
And if you do, would do this then,
with the open call, that could be maybe not a best call.
But if you put out maybe with just a week call,
and just say, OK, if they know that the data is in irons,
in the database, you can access it.
You can maybe just use the week call, and all of right doors.
Final job.
Just to come and see you mentioned,
you asked for a few other similar efforts.
I believe there's an important statement,
just for people that need this.
Something from the system,
or bring the platform for analysis.
I don't want the state to order out of the team.
That's from the TSCS.
There's no sweet state to say this data sends it out.
OK, what's the name of the rainbow?
One of each of it.
OK.
What does it mean?
OK.
It gives you beer.
OK.
All right.
Yeah.
Just wrap up.
Thank you.