Welcome everyone. My name is Ricardo and I have been working on Geeks for a couple of years already. This is going to be a gentle introduction to functional package management, which means that I'm not going to define what functional package management is. Instead I'm going to start with a bold claim. Package managers are really useful. Who disagrees with this? No package managers are really useful. This is a meme in computing. It's been around for a while and there are different variations of it, but it has survived so far. But they can be so frustrating. Who has never had a problem with packages before? Installing software and... I actually could skip all those slides, but for the benefit of the people who are watching from afar, these are just off the top of my head a couple of issues that I've personally encountered and that probably have shortened my lifetime. The first thing that you will encounter when things go wrong is version conflicts. You may want to have a particular version of the piece of software and it's not available and you can't really just install that version that you want because that would conflict with what is already there. This leads us directly to the other problem, which is that usually old software is available because harmonizing all these dependencies between different packages takes a while and it's non-trivial. So as the dust settles, actually the software world has already moved on. So there are always a few steps behind. Upgrades can be very suspenseful, which is why in the past I would not touch my computer before giving talks or before deadlines. I would actually really just try not to upgrade because I want to use the computer. Because the only way is forward. You can't really go back. Once you commit it to an upgrade, it's really hard to downgrade in traditional systems or those systems that I've encountered anyway. And it gets worse twice as bad when it's not just you using the machine, but if it's a shared machine. You have a computer at home and it's you and your kids using the machine and they upgrade because they have food. They shouldn't.  And that's bad because as we established already, the only way is forward. You can arrange yourself with it like switch jobs or become an artist. And trust. Trust is an issue. How can we be sure that the software that we install on our machines is actually the software that we want to have installed? This is a really hard problem and a lot of people are working on this. There's a whole community of people who work on reproducible builds that give us the tools to at least challenge trust issues. So we cannot be sure that we can fully trust things, but at least we gain some confidence in that the software we are running is actually the software that corresponds to the sources that we've read. There are a couple of partial solutions or attempts at solving things. These are just a few that I've encountered so far. The first one is obviously just don't use package management. You have a compiler and you know how to use it. If you don't, then that is a problem. It's not a solution for you. It doesn't only extend to the package itself, but it may extend to packages that are different versions recursively. Dependencies for that package are the different version than the one that's provided by public repositories. So you might just rely on other people doing that work for you by using external repositories that provide pre-built binaries. So in enterprise environments, people often use this Apple repository. On Ubuntu, it's popular to install and enable PPAs, where you can just download packages that other people have built. There's a user repository for Arch, GNU, plus Linux. Usually the solution comes with a host of other problems. You may have not the original conflict that you started with, but you may have additional conflicts in trying to harmonize these different repositories, the official one and the external one. There's even more software that you have to trust, where you may not actually have the tools to establish trust. Another common approach to solve the problem is to use application-specific package managers. It seems like every language has its own package manager, and if you have a non-trivial piece of software that is written in Ruby and Haskell, and maybe a sprinkling of Python, then you may have to use gem, cabal, and pip. This is not just one tool you have to learn, like your system package manager, but gem, cabal, and pip. And they all behave slightly differently. They all have their idiosyncrasies. So it's more packages, but less management. Just devolving this to a language level, which is just a little bit better than doing it on a per-package level. You can also build your own system packages. If you're using apps, you could write a devian package, and who does this on a regular basis? Who enjoys doing this? Or you could use RPM. This is kind of hard to do, because again, you've got the same problems as with using no package management at all. You've got to solve all these issues first, but you're rewarded with a binary that eventually breaks as the rest of the system moves on. You've got to rebuild things again. You can also automate that. You can generate RPMs, and you can generate devian packages with things like FPM, but I don't know, maybe it's just me, but I feel this is really inelegant, because it generates so much boilerplate stuff just so that you can install software. It doesn't adhere to any particular standards. It's weird, right? I used it before because I wanted to distribute software to people who may be using devian and people who use RPM-based systems, so I wrote an FPM package and built all these binary archives that people can install. This helps a little bit for lazy distribution of software, but it doesn't really help users themselves. A very popular solution nowadays is to just give up and say packaging is really hard, so let's not do it. Let's just shrink-wrap the whole environment and distribute that binary blob to other people who can then run that thing. Introducing functional packaging. Functional here does not mean it works. It does work, but that's not the meaning of the term here. Functional means just like a function, like a pure mathematical function. So that's like a metaphor. So this is the function here. I see you can actually not read the top. This doesn't matter, right? So you treat the build process as a function that has inputs and produces some output. Inputs for package build process would be the header files, the sources, all the tools that you need to build something, all the libraries that you would need to link the software with, and outcomes, some binary artifact, a tree of files. In this case it's Emacs, which generates a couple of libraries and a couple of binaries that you can run. Now one thing that I would like to stress here is that with functional packaging the target directory includes a hash of all the inputs, which means that if you change one input, and it doesn't matter which one and how far up the graph it goes, you will get a different output directory, which means that installing or building Emacs with this version of GCC is going to yield one output, whereas building Emacs with that other version of GCC will yield a different output. So you can have different variants of a piece of software and it is not just dependent on the version. It's not just, I want to use Emacs 25.1 and I would also like to have Emacs 24 or something. So you can have different variants of Emacs 25.1 if you wanted to. And all of the inputs are encoded in that hash. So it gives us a unique new namespace to which we can install things. So input means you get the same output, ideally, and with different inputs you get different outputs. The way this is done in Geeks is that we've got this Geeks client, a client-level tool that a user, an unprivileged user can run, that Geeks client talks to a demon, runs as root and performs things on behalf of the user. The things it performs is, the abstraction is that it spawns isolated build processes, isolated environments, fashions, isolated environments that give a new view on the system where only declared inputs are available. That means if I were to tell Geeks to build Emacs and I didn't say that I want to have a compiler available, then that build would obviously fail. So I have to say I want to have a compiler and I want to have this and that, and the demon will comply and create an isolated build environment where that compiler that is specified is available. All the libraries that I want to have are available. All the other packages, things depend on, are available. And eventually the build artifacts are in a store. In the store... Everything eventually ends up in the store in its own name space, in its own prefix directory. But these prefix directories, they are really, really long. They are ugly. There is something like slash new, slash store, a really, really long hash minus the package name, the version number. And then you've got slash bin or slash label, whatever. Nobody in their right mind would like to memorize all these hashes so that it can use Emacs. This doesn't happen. So to simplify all of this, there is the notion of profiles. You can't see this up there, but this is my profile. It reads as slash home, username, dot Geeks profile. And this is really just a link. This is a link that points to the current Geeks profile, somewhere in a state directory, which points to the current version of the profile, which again is linked into the store, to the actual profile, which again contains links. It's a union of all the things that should be in my profile.  But these are just links to the actual tools. In the store, we've previously built SEMtools, so my profile just references SEMtools in the store. It also references Botite, which is in a different output directory. So profiles are unions of all those individual trees with their practices stripped, and the current version is really just a link to the current version. So if I were to remove a piece of software, I'm not going to modify anything in there, because the store is immutable. Instead, what I would do is create a new generation of my profile. Now it's generation 43, which points to a new profile, which no longer contains the package that I removed. But if I wanted to, I could just go back, right? I could just change the Geeks profile link to 42 again. Go back, go forth, and back and forth, and back and forth. Nothing ever changes really, so the store only grows. Until I decide to delete that link, the 42 link, which then shows us that the profile itself is no longer referenced by anything, so I can run the garbage collector and collect that unused profile. So before I move on to something funny, I'd like to demonstrate this. Can you see this? Maybe like this. Okay, I'd like to read you, but I can't, because I don't have the hello command. So as an unprivileged user, I install the hello command. It tells me that it will install hello 2.10. I guess it says hello in a fancier fashion, but I don't know. And it installs that somewhere into the store. So there's a slash news, slash store, a long hash that is highlighted here. Hello, something, something. We can take a look at this. Inside of that, there is a bin directory and a shadow directory. This is a real tree, right? What you would normally have at the root. Now, I can greet you. But this is kind of artificial. I never had to install hello before, except for demos like this. So let's install Python. So it tells me that Python will be installed somewhere into the store. And it also tries to be helpful and tell me what I may have to do in order to use it, but I don't because it's... yeah, so here it is. I realize I'm in the guile dev room, so I shouldn't be using Python. So let's remove this and use guile instead. As you can see, this is a transaction. I'm doing this at once, but I'm removing Python and installing guile in the same transaction. And now Python is gone, right? There's guile. Now, this is what happened. When I installed hello for the first time, that created a profile, generation one. When I then installed Python into my profile, it added Python. That means it created a new generation that included Python. The previous generation is still available, right? It's still there. It's unmodified. I could go back to that. Generation three, where I've removed Python and installed guile. So what's currently installed is this, right? Hello in guile. For some reason, I want to go back and undo a mistake, which it was. It was no mistake here, but this is just for demonstration purposes. I'm going to switch back again. You see that generation two is now the current generation. And now if I want to use Python again for whatever reason, it's there again. And guile is gone. I'm not going to show that though. So rollbacks, the feature of having generations and appending only to the store, gives us rollbacks just by changing assembly. That's beautiful. We can also install software into different separate profiles. So we could use one version of Emacs and compare it with another one if you wanted to. Or in a scientific environment, you could install a whole workflow into one profile. And for a different project, you have a different workflow. You can use both of them. So this is beautiful. This is all completely isolated. My changes here will not affect any other user. They won't have to use Python if I made the decision to use Python. If I install it into my profile, it really only affects me. So the way that this works is by using scheme. The geeks is written in guile, which is an implementation of scheme. This may look confusing at first, but let me show you first a couple of things about scheme. So these nail clippings, they are important. Everything is a parenthetical expression. And the first thing in there is special. Everything that follows is just an argument to the first thing. This is a simplification. But in general, this rule applies. Whatever is first is kind of special. It may be a function. It may be a special syntax. In this case, we have a list, an expression, an S expression that has three elements. The first one is the function plus. The other two are arguments to that function. Now what I can do is I can quote expressions. That evaluates to the list that contains three elements. You can think of this as a toggle switch. Right now it points upwards, which means data mode. All of this, what follows is now data. It's not going to be evaluated. But you can flip the switch down and enter code mode where things are evaluated. And now this no longer looks that scary, I think. Maybe that was too optimistic. So we are defining a name. I say that this name GLPK is whatever follows evaluates to. This is a package that has a name, obviously, and it has a version. And it has sources. We don't care so much about this right now. Let's get to the build system. The build system is the GNU build system. Configure, make, install. Oh, there's two back. And here you see the toggle switch, right? So we've got inputs. And that is an actual package. Just like that. Okay, we have time for questions. Can we ask the next people to set up? Yeah, questions. If you want to learn more about GLPK, come to me afterwards. I'm quite familiar with the name. What's the link with the case of 4 or no link? I was waiting for this question. So the question is, what's the difference between Nix and Geeks? Okay. I'm quite aware you have to see what the link is. Both Nix and Geeks are implementations of the same principles, right? Both of them are functional package managers. Nix is older than Geeks. Both Geeks is a different implementation that uses skin throughout, which has wide implications on a lot of things, actually. This would deserve another talk. So there's a lot of differences that come from that initial design decision to use skin. So Geeks uses the Nix demon underneath. And the derivations they use are the same, the same format. So I think in principle they are compatible. But everything above that, everything that's not low level like this is very much different. Okay, do we have time for another one? Sure. We have similar as Nix OS, where you have the integration. Is there something similar like Nix OS? People may not know what Nix OS is. A distribution, a new distribution that builds on Nix. And yeah, for Geeks we have this too. It's running on this machine actually. It's called Geeks SD, and it extends the ideas of Geeks to the operating system level and has declarative configuration of the whole operating system. Also in schemes. Same kind of thing. Is there a way to delete generations on your own out of this space? Is there a way to delete generations? Yes. You delete the link. So there's a command line thing for deleting older, profile generations.  Yes. How do you deal with security updates? Security updates are handled by what's called graphs, which is an optimization. But to actually explain how this works in detail, I'd rather not do it right now because they would take a little too long. It's documented, and you can find it in the manual, which is really extensive. Or we can chat later. Yeah, I would like to chat. Okay, cool. That's it. Thank you.


Hello, morning. We're just about to start. Sorry for the delay. We had some issues. Some technical issues First of all, Ida Martin the head of the research service will address some words Yes, sorry for the delay, but sometimes with the informatics this kind of thing happens. Okay. Thank you for coming here I'm very happy to see this room full of people interested in in Maria's kudoska. Could he action in the Oval of G Today we have an information day. This is organized by research service while we Okay, this is the star. Sorry. Well, the main name of this section is to help all of you to prepare a successful proposal and To try to resolve any question any issue that you can have at that moment or maybe in the future because this time You know all of us. Well, um, to this aim We have three speakers today The first one is you said me go as probably, you know, you said piece the EU projects manager of the Research office here at Citadella. He has a large experience in individual fellowships He will tell you very briefly some features and characteristics about the this program about the individual fellowship Second of following we have Gemma Revolta she's here Gemma is the she's a director of the studio Center for Science Communication Society of the UNIFS at Pompeo Fabra She's also a professor of the experimental and health department She's also a coordinator of a project European project called Harry about the about responsible research and innovation She has a large experience in European projects. She has a large experience in communication. That's why she's here We have realized in in individual fellowship We have realized that an impact in communication is one of the weaker points of the section So Gemma will help us to address properly the section in your proposal and and the third speakers is Dr. Georges, you know, please, you know, look Paulus sorry Jordy for friends Maybe easier for us He's a researcher a professor of the Department of Humanities he is An specialist in cultural heritage. He is now here because he has Participated as an evaluator individual fellowship So he will provide all of you with a view of the evaluator probably what is the more usable views because he Can't give you that some tips to for your all your proposals. Okay after the this is our Presentation there will be about 20 minutes for questions Finally just to say that this section is this session is It's being broadcast live So you you can see again if you consider necessary on our website and Presentation there will be also available on the website. Okay. Let's start now with the first speaker. Yes, and you Thank you. Well, thank you all for being here today As I said, I'm present manager here at UPF at this campus and basically I deal with social sciences Projects we have here today with the other present managers from the research service as well Regina and Eos and Paloma who if you're applying to if you're Thinking to apply to a Marie Curie head UPF will also help you depending on your On your on your department you will apply Since most of almost half of my time has already gone by I'll I'll try to summarize what I was Supposed to do basically because they are mainly administrative issues And I think it's more important that we can get the advice from from Georgia's or from Hema who are more Specialist in these topics and we are always happy to answer any question that you may have Not only today after the presentations, but at any other time So as you may know Marie Curie's are part of the excellent science pillar from for the horizon turning to any program This means that are supposed to be like really impressive projects devoted to Focused on really good researchers Their main objectives are the to support best researchers at any any time of the careers with the main characteristic that you must have either your Your postdoc your PhD or have four years of full-time experience It doesn't matter if you don't have the postdoc at the time of applying as long as you can prove that you've been four years in full-time in research There is a very important aspect of Marie Curie's which is mobility not only international But also intersectoral and interdisciplinary International it's obvious you will be moving to another country, but keep in mind the intersectoral and Interdisciplinary aspects. This is something that they really take into account as George's will Explain us later and also take in mind that is a good opportunity to move from another sector not only to stay in the In the academia so that is a good opportunity to also Grow your networks as All of us almost all of the excellent science pillar. It is a bottom-up project So all fields can be fine can be You can apply from any part any Approach humanity science technology doesn't matter So all of you are more than welcome to to apply for that because all of you have same opportunities I will try to go a bit quick There are some transversal concepts that you must have into That you must have in mind when when doing your proposal We have highlighted three of them. One of them is responsible research and innovation are all right this is cross-cutting issue in all horizon 2020 projects and It implies open access implies gender aspects. It implies Sustainable research and innovation. It implies making an easier making easier Access to the results your scientific results formal and informal science so basically there is a lot of information about this in in all the in several websites of the Horizon 20 we can help you with that but keep in mind that you should focus not only in your research project But in how this project will help you and will help other people and in a sustainable way Open access is mandatory in all horizon to any projects Depending on the field you are the rules are a bit different But basically what they say is always keep make your project as open as possible as close as necessary So if you have that which is very sensible, maybe you are not supposed to to make it all in public But maybe you can do a summary or something all your publications must be open at some point And finally gender aspects This is something very important. The European Commission takes it every time more seriously And as we will see there is a specific point in the in your proposal in chapter 1.3 Where you are supposed to talk about? gender aspects of your of your project Basically you should take care about sex and about gender so not only about differences between men and women but also differences in in the society features and cultural features that men and women Deferring so if you are doing a project about car accidents, for example, you may consider what happens if a woman is pregnant It's not the same having an airbag for a man for a woman or for a woman that is pregnant differences may change and This is very important because you will see in the reports that they take care about if you have addressed gender or not in case it is it is necessary in your project and some of the aspects we've seen and some of the Advices we've received from the European Commission It's this very last paragraph that being blind to potential differences of sex and gender may result in missed opportunities So it's not only that it's important But it also it may give you an extra point if if you address properly gender because there may be small groups that may Need this this different approach What's one of the most important things or the things that people like more about Marie Curie? Is the salary especially if you come to Spain and It's like well, it has nothing to do with any other postdoc that you may that you may see if you go to our countries, there's a coefficient a coefficient rate, but Basically as I guess most of you will be coming to Spain You may you may like to see that you get like 45,000 4500 Gross per month plus mobility allowance and family allowance if you are eligible at the time of submitting your proposal There will be maybe I mean this is not in the net, but there will be some taxes maybe well for sure and and also It's good to know that you get 800 per month in research activities And that the university or the search center where you're going It's also is also receiving some overhead so they are always like it always Looking forward to receiving this kind of what project because basically they are free for them What's the expected profile or what do you need to apply for a for a Marie Curie? You need the applicant so the researcher you need a scientific supervisor and you need a host institution So it's quite straightforward. You have the researcher. It's yourself You probably know some scientific supervisor from for your experience And this supervisor is working a host institution. So you have the pack And as I said, you need to have either the doctoral degree or for years in in full-time experience In in research Well, I see some of you that are taking notes and all these presentations will be Send to you. So it's don't worry about that. I know I'm speaking quite fast, but But time time is limited And we have four different kind of of Marie Curie or we'll we'll talk about four different kind of Marie Curie There are the European fellowships and global fellowships and within the European we have three different three different kind Basically, the standard European is what most of the people apply to Then we have career start panel for people who have been at least 12 months out of the academia And then reintegration panel for those Who are away from Europe or have just arrived to Europe and and want to stay here for a while and then global fellowships Are for people who would like to move outside the European Union stay one or two years there And then come back one year at the European Union and the return price. It's mandatory there is here a kind of Summary and then one important thing is the mobility rule If you apply for a European fellowship or a global fellowship the country where you are going This you have you are not supposed to have spent there 12 months in the three years previous to the deadline So 14th September 2017 If you're applying to a reintegration or a career Restart panel then it's three years in the last five years It's a bit easier important in the global philosophy piece The country where the mobility rule applies is the country outside Europe So if you are staying here at UPF for example at the moment You could go to the US and then come back to you BF as long as you have not been at the U.S More than 12 months in the last three years What important thing is that regardless of the type you choose You can go in a second man to another institution Then there is always a bit of confusion between what's second man We've tried to to make it easier for you Showing the difference between a second man and a short visit So a second man is something it's a stage that you do in another institution which must be in Europe Which has an impact in your project and it's something you've planned ahead You will you would go to that other institution? University research center It can be any kind of it you will have a supervisor there and what you what you do there It's important for your project. It has without that you could not develop your project Whereas a short visit Maybe a visit to an archive for example something that at a certain point of the project You will find out that it's maybe interesting to go there to spend some time But it's something that it's more informal. You maybe don't don't have a supervisor over there or it's something that it's not Not that important For the project for you. It's of course important, but not for the project and Then depending on the duration of the project the fellow the second man can be Can be maximum three of three months or six months as most of you will be applying for at least two years? Because the effort is what is if you do therefore it's worthwhile applying for two years Then you will have a maximum of six months This doesn't mean that you have to spend six months All together you can separate it in several in several phases of two months one months one months at the first At the beginning of the project then three months at the end Whatever it doesn't matter But it's important that if you know that you're going to go on a second man you put it in their project because this It's not that it's mandatory, but it gives you quite a lot of points, especially if it's into in the non-academic sector Then you have here the the schedule of this year's call Important thing deadline 14 September. There is no opportunity to apply later if you forgot Document if you forgot anything, there's no second chance Results are probably appearing in late January beginning of February 2018 and projects should start around May 2018 And from that day you have one year to start a project so between May 2018 to April May 2019 You can start your project the application It has two separate play two separate parts An administrative site which is quite straightforward for those applying at UPF. We can help you with that It's quite simple important here is that you have to select an evaluation panel This is very important because that the panel that you select is for whom you will be evaluated So if you're not clear belong to one choose that one which can best appreciate your CV and your project and Then there are some keywords that you have to write there And please list them in Relevance order the first one which you will select is the most important the most appropriate to your project Then don't don't mention all areas if you are an archaeologist and there is a little bit of biology Just don't put biology because it's probably not that relevant and Putting biology would mean that maybe a biologist would evaluate your project and that person may have no idea about archaeology so You may lose some points there Then in the industry in the scientific part. There are three parts excellence impact which I will not go through it because Gemma will talk about and implementation The excellence has these four questions. I will just highlight some Some of the most important or what we think it's most relevant there basically in the quality side You have to highlight the state of the art of the project say what's what has been done in that field since now And what your project will bring what's what's the impact that your project will have in this in this part You will know about your project. It's probably the part that you do best so just Go ahead. Just don't be don't be shy and and show that you know about this topic And that you know what will happen if this project is is Is funded that you will the state of the art You will go through beyond the state of the art that you will publish how many whatever number of publications, etc a Second point important training Remember that Marie Curie is not only a scientific project. It's also training So you have you have to prove that you will learn in scientific Aspects, so you lack in a know a methodology you lack in some specific point of your project And also that you will learn in soft skills writing grants management Ethics gender aspects all these kind of things that you may think out we can also help you with that But consider that it's not remember that it's not only scientific There are also the site the soft skills, which are important And that you have to prove that you will also bring something to the institution you are going So it's not you learning but the institution where you're going has to take advantage of your knowledge there as well for this for in order to learn and To take advantage of the project you need to have a supervisor. It's important to prove That this supervisor has experience not only in the topic that you are talking about but also in the training of Researchers, so when you talk about him or her Please mention how many postdocs? This this supervisor has Supervised if there is any of them who holds a role in position now Then just mention it so that to prove that it's an important person or that knows how to train people at least and Then you have to prove in the first in the fourth point that You are regardless of your of your level in your career that you are a person that is willing to take advantage of all opportunities To grow so that you have a professional maturity enough that Anything that you received in this project will let you Develop that you will boost it will boost your career and let you apply for an ERC for to know to start Leading your own research group Etc. Then the second point is impact. We'll not talk about that and Finally implementation here is I think well with impact where you most of you have the biggest trouble because It's not really a research approach. It's a lot of blah blah blah And if it really is about how well is the project how organized it is and how good is the solution where you're going If you've gone through the template you will see that there is a mandatory gun chart Which should prove how good is your work plan? We put this one here. It's from a Marie Curie that was funded last year to show that It doesn't need to be something very sophisticated here There are seven lines with the word package the liberals you will have to submit milestones and then the impact So there is a one line for the conference one line for dissemination Meetings with our groups and project management So it should be something easy simple and that the evaluator can really see that you know What you're talking about and and have a clear image of of your project remember that the evaluators may read 15 20 projects and if you put something really messy and they just I'll try to freeing project. So make it very simple for them. And then we have these other three questions the first one in this light is quite important because Since a lot of people ask for 24 per month project, you have to prove that your project really needs these 24 months So plan ahead mention How long will all activities be why would you need to be paid for 24 years in such a good salary? Maybe they consider that with 18 months is enough for your project Mention, why would you how would you use the funds that they will give you if you will need to hire someone? Maybe to to some parts which are not so relevant in scientific terms to save you time for example How how would you you will divide the word packages in terms of months? Why would you need four months for analytical research? Maybe Etc. So make it easy for the for the evaluator to to see that your project is well structured and that really needs all this time And then the other two questions are more related to a the institution where you're going My suggestion with this is that you ask the international services there Or if you're playing to UPF ask ask us and how to to to fill this question and About the management structure and risk management. It is important to to have contingency plans Even if your project, maybe it's not you don't see any risk Evaluators always find some risk there some bottleneck or some point that may risk your project. So Include them and say how you will overcome them if they happen Then about the CV. Well, I probably you are tired of doing different kinds of CVs Also if you're going coming to UPF we can have you with that Finally, there is also this Late table you have to to fill in it's also administrative issues So don't worry much about that. We can or the institution where you're going can help you with that as well And ethical issues, this is a quite important aspect They will not turn your project down because of the ethical project aspects at first, but you should be aware of What if any issues you may have because once the project is granted You will have a limited time to prove that that you're aware of of the specific circumstances of it And to show our to send submit a lot of documents So think ahead plan ahead and start if you need informed consent documents If you're doing interviews if you're doing experiments think of what you will need and at least inform them of Okay, maybe I don't have them now, but I'm aware of what is needed and if it is the case I can I can submit them in one month for example and just a hint on evaluation The of the three parts we talked about Excellent is worth 50% Impact 30% and implementation 20% So you may think okay, excellent. This is where I'm good. This is their research It's important. Okay, I'll get the most points over there And maybe impact and quality and if it's in chief implementation It's 13 20 percent. Maybe if I don't make such a big effort. It doesn't make the difference You have to aim for the hundred points in all the parts It's a very It is very challenging to get these projects. You should aim at least to have in 95 out of 100 points So all parts must be perfect. So do not leave anything for the last minute because as George's will tell you He's seen a lot of good research proposals with bad impact maybe or what Implementation aspects, which then they are turned on and finally here with us We are quite behind on time and there are some slides about general tips and evaluation Like actual evaluation reports some sentences that people from areas have been keen enough to let us Show you which you will be able to read them when we send you the presentations Here they're like all these comments and Well, thank you. I know I've been quite Fast apologize for that, but I really think that what Hema and George's can offer you today is more important It's more relevant makes it what makes this session probably worthwhile if you have any question, please do not hesitate to send us an email to this address if you are applying to UPF, please also say which department you are applying to so that the Relevant project manager can answer you and provide you a more personalized service and Well, thank you all for your attention