So, you guys, we're going to get started now. We have Sorna and Bhushan from Avi Networks going to present, so let's give them a round of applause. So, guys, take it away. Thank you very much. Okay. So, welcome to the, first of all, thank you for the control team for inviting us here. I'm Sorna Padila. I head the product marketing team at Avi Networks and I have Bhushan here who is part of the technical marketing team at Avi Networks. We just will quickly walk through how we work on the web-scale elasticity and how we can accomplish automation in terms of an open stack deployment with our open control integration. I also have Ankit from the control team. If there are any more questions, first of all, quick check. How many of you know what Avi Networks does? Wow. I'm impressed. Thank you. That's more than half of the audience. Awesome. Okay. So, I'm good to go, right? You all know about Avi Networks and I can leave. I'm kidding. The one way your knowledge about Avi makes it easier is that I can flip through my slides and just give it to Bhushan for the detailed demo. Just for those few of you that are not familiar with Avi Networks, we are a software load balancing company and the reason why we kind of start with software load balancing is because web-scale is here for computers. So, when you look at the storage and compute layers, it's elastic. You deploy the bits on any off-the-shelf servers and you can reallocate, readjust the capacity or utilization based on the requirements on demand, on the fly. It's elastic. You use commodity servers, so you kind of bring your server investment, infrastructure investment down. You manage it as one because you have a centralized controller that can take care of all of these kind of resources and it's highly automated. You get the telemetry or the visibility into what's going on so that you can then automate and readjust your resources. It's elastic. However, when it comes to networking, there are single-purpose appliances where the control plane and the data plane are fused together. It's not elastic. It's rigid. It's you configure or provision, rack and appliance. It does only load balancing and not beyond anything beyond that. And it's kind of like a black box where you don't know what's going on inside it. Data goes in, data comes out, but you have nothing, no kind of visibility in what goes on underneath it. So what we did was instead of having HA pairs in each environment could be your private cloud, public cloud or container kind of environment, what we did instead of going with the fused approach was separate the management plane from data plane. We said that, okay, let's go with the kind of airport analogy where our airplanes become the data plane. They come in, they go out. That's all they do. The pilot just blindly follows the instructions from the air traffic controller, lands, takes off, boom, done. And then the control plane is centralized, similar to air traffic controller that sits off path away from the runways, sits off path, tells the pilots exactly at what height, at what speed they should start descending, to what gate they should arrive at, what runway they should be taking. And if there is already a plane at the runway, they know that. So they are going to divert the traffic to a different gate. They're going to divert the plane to a different gate. That's the kind of intelligence that ATC gives to the pilot. So the pilot can only focus on bringing people in, like bringing packet in, bringing packet out. So the controller sits off path, has the cycles to munch through this telemetry that they get from load balancers and then deploy these service engines either on bare metal, your private cloud, public cloud like OpenStack, OpenShift. And then there's the VMware environment containers, Kubernetes Docker or Mesos clusters, or even public cloud like AWS, GCP, and Azure. And because we have the visibility with what's going on, we can also integrate with the rest of the management orchestration layer providers to make it even more extensible and automatic to make it programmable for you guys to deploy the applications or resources by automatically. And because we have the visibility, you can now get insights into if an application is slowing down, if there is high latency, what exactly is going down? And I get a notification when there's high latency, I get a notification or when there's a web server that went down, you get an alert, your admin gets an alert so they can take a quick and immediate remediation steps rather than waiting for someone to point out and say that, hey, this is not working. And as opposed to physical appliances that can only scale up, which means that you can only buy more appliances, we are software, so you can either scale up, get to a bigger service engine, which is our load balancer, or you can scale out, add more service engines, or you can do a combination of both. But as your traffic increases on demand, and when your traffic recedes, you can kind of bring it back in, scale it back in and free up those additional resources for any other purpose. So that's the kind of structure that Abhi has. Now, coming with OpenContrail, how we integrate is, if you have an OpenStack deployment, we, at the configuration's setup stage, we take the input from the, like we work with Abhi controller at the bottom, works with the Neutron server, takes all the credentials, like keystone credentials or anything from the Neutron server, passes it on to the Neutron server. And the Contrail client, it works with the Neutron server. It takes every update or every change that is passed on through the Neutron server. And then once you define the provider to be the Abhi networks, it has the intelligence, the service monitor has the intelligence to divert the traffic to Abhi networks as your load balancer provider. And how do we automate it? We integrate with multiple projects, like, I know this is the night chart here. Horizon, Nova, Keystone, Neutron, and Elbas. We have an Elbas plugin and we support V1 and V2. But what it does is you provide the Keystone credentials and the location of the Contrail server. And we use Elbas. I mean, you can either use Elbas or Abhi API to set up the configuration. And after that, Abhi controller takes care of the automatic deployment. We use Keystone to set up the user profiles. We spin up the service engine VMs, which are the load balancing VMs, as a Nova instant. In the correct time, we know where to place the load balancing instance, the VM. And we place it in the appropriate Neutron by talking to, I mean, we place the VM in the appropriate network by talking to Neutron, getting the information from Neutron. And we also allocate the VIP and using the Neutron API. And binding the VIP to the secondary IP as well. And associate the floating IP to the VIP. So all of these additional processes, which could be manual on auto-scaling load balancing fabric, like spinning up another load balancing, more additional load balancing service engine as the traffic grows up. All of these are completely automated. None of these steps have to be manual. And because we also get the analytics, as I mentioned earlier, because we get the analytics, we have integrated that into Horizon UI. So you can either add it as a tab in your Horizon dashboard or pull up the entire ABI dashboard into Horizon itself.  I know the last line is not visible probably at the end, but it supports OpenContrail and JuniperContrail 3X and above. But we support pretty much everything from an OpenStack perspective. Just to give you a quick sense of how easy it is. This is a snapshot of the ABI dashboard. There is just one checkbox over there that says integration with Contrail. And that will take you down the path of setting up the Contrail server as well. You just need to give the location of the Contrail server. It talks to the Contrail server on the back end. And here are a couple of screenshots that I have here, but I think Bhushan will show it in his demo as well. You can either bring just the analytics as part of your Horizon dashboard. This is the ABI analytics, where it shows the per hop latency. As you can see it from when your client hits the load balancer, when your load balancer sends it to the server, server sends it to the app server, and then the database. How fast is the data being fetched? So it gives the per hop latency, and it gives the granular details at the bottom per transaction. Could be a significant log. Could be a significant log. But we get the transactions or the visibility for each and every log that we collect. And this is the other way you can get where you have your entire ABI dashboard in your Horizon itself, as opposed to this, where you just have it as a tab, just the analytics as a tab. So there are two ways of deploying ABI. And with that, I will stop and have Bhushan show the demo. Any questions? Sorry, before I let Bhushan. Yes? That will be Bhushan. Can you repeat the question again? I'm not sure about the scale in terms of that right now. I'm sure we have the numbers up there on our KB. Let me get back to you with that answer. Yeah. OK. Moving on to the demo. So like we saw in the presentation, we can either run directly with our LBAS plugin and configure the load balancing using normal LBAS, or else we can have the whole ABI dashboard right in the Horizon UI, like you see out here, so that the people can directly use AVI's API on the UI. So everything we do on the UI and CLI are backed up by REST APIs in the back end, so that users can directly use AVI API to configure load balancing with much more richer features than they get with normal LBAS APIs. So what you see out here are the same. Even if you configure something using LBAS APIs, we map them to AVI. So let's go ahead and see how easy it is to create a new virtual service or a VIP. Just give some name to the virtual service. Test VS. VS. And we can auto-locate IP addresses based from the networks you have got. So I'm placing the VIP in the client network. I can also assign a floating IP real easy. We can select servers. We can directly give the IP addresses, or I'll select servers, selecting them from a certain network, just add the servers into the load balancing pool, and choose what type of application you want. Is it HTTP, HTTPS, what kind of certificate you want, and just save? And within seconds, the new application is up. So AVI is split up into two parts. There's AVI controller and the service engine. The service engine does the main act of load balancing. The data handles the data path. So if the service engine is already available, the only thing the AVI controller has to do is push the configurations and connect the service engine to correct networks based on the VIP and the back end pool members, and the service is up. If not, it will go ahead and deploy a new service engine and then connect it and get the application up. This is just a brand new application, but let me move to another application I have out here already running, which also has a lot of traffic on it. So as you can see, we can show complete end to end time, not just on real time, but also past historic data. The amount you can show out here depends on the size of the disk you allocate to the service engines. We can give a kind of a summary of what the client latency looked like, what the server ITT is, what kind of app response you're getting, and what data transfer is. Not just as a summary view, but also at each and every point in the time on the graph. If you want to dig in more how your application is performing, you can switch to logs. Now we classify the logs into two parts, significant and non-significant. The significant ones are the ones which end up in 404s or some kind of errors, or take a really long time then expected to complete. And the non-significant ones are the ones which end up with 200s or end up without any errors. So you can explore even more. For example, if I expand one of these logs, we see that it's coming in from Mexico, what kind of OS it's using, what kind of browser the client is using, the certificate type, the TLS version, which load balancer on your setup did traffic hit, which back in server pool it went to, and what was the kind of URL, lots of information out here. Everything you see out here in blue can be filtered in a Google search kind of a way. For example, if you want to search all the 404s you got on your application with just one click, you get all the transactions which end up in 404s. More than that, we can do SSL termination. We can do SSL re-encryption so that we have end-to-end SSL. We have a really feature rich, when it comes to layer 7 features like content switching, redirection based rules.  For example, out here, my application is getting simpler attacks. And using the layer 3 policies, we can also, with just one click, block any of the attacks right then and there. So that was all I had for our demo out here. If you guys have any questions regarding AVI, feel free to answer them. All right. So we talked a little bit about the spinning up of the AVI instances, whether the control plane or the data plane. And it sounds like they're virtual machines, right? Is that correct? Is there any plans for containerization in the future? We already support containerization. We work as a container in OpenShift, as a Docker container in OpenShift Cloud or Kubernetes or Mesos environment. We do have the support. Did you want to show the scale out demo? Scaling up. Yes. Yeah. How to set up autoscale or those kind of things. OK, sure. So we also have intelligence of setting up something, autoscaling our application based on CPU utilization. Let me move to tenant view. So here in this tenant view, you can see the list of tenants when he's switched. Shows that you can provide self-service provisioning for your application team. So when your application team is ready to move from local development to either production setup or testing or even just production migration, they can take their load balancer and set up and provision their own load balancer instead of waiting on a networking team. So you have these agile methodologies for app development. But once you go to app deployment, you kind of slow down. So it's kind of like rushing faster to slowing down, only to slow down, to be slowed down by the networking team. So instead, you can provision self-service load balancing slivers for them so that they can provision their own load balancing by the time they're ready for deploying their application as well. And this is the autoscale? Yeah. So in our view, we have a concept called service engine group, which is just a logical grouping of the service engines based on common properties. So in that, you can set the kind of HAA mode you want. We support a normal negative active standby. Then there is an active active mode in which you can have two or more service engines running active, active, active. It need not be just two. Then there is N plus M buffer mode, which is, I would say, most preferable. Because in that, we have N service engines running active and M buffered. So the buffered service engines constantly sync with the on the connection states. But they don't take part in the traffic as soon as one of the active service engine goes down. We can use one of the buffer. Buffer automatically takes over the traffic. So while scaling out in active, active, or N plus M buffer mode, we can use a feature called auto rebalance in which we can program the CPU threshold, which Avicontroller looks out for. If the CPU of the service engine goes above a certain threshold, it can scale out the application to multiple service engines. If the traffic goes down, the CPU utilization decreases. Again, it will scale that back. And if it sees that some of the service engines are just lying around handling no traffic, it will also delete those VMs so that you save on your infrastructure resources. Apart from automatic scale out and scaling, you can even manage per application-wise. You can scale out manually. If you see a current service engine has some problem, you can even migrate it out to another service engine. Pretty easy. Everything in the UI is like a few clicks away. So any more questions? Yep. I wanted to. So if you have a question, can you say it on the mic? So is there anything special in this with OpenControl versus standard OpenStack Neutron integration? So the part which we integrate with OpenControl is we provide automation in OpenStack whenever you configure a new virtual service. We have the responsibility of configuring the service engine and connecting it to a proper NICs and all. So that's where the OpenControl integration comes in. We read in the data from OpenControl so that we know what overlay networks we need to connect it to. How can we program the floating IPs to the WIPs and all? That's the part where we talk with OpenControl. Yes, I would say it's added benefit when you have extra features which Aviv provides with OpenControl, extra features of load balancing which you won't get if you go with a normal LBAS running with OpenControl. And yes. No. So the integration comes into play has to be supported using OpenStack Neutron, right? Let's say that you have an OpenStack automating LBAS using Neutron phones and you decide to choose OpenControl as the SDA over the Neutron. You use Aviv over HAPocs because of the obvious difference. So you're existing in OpenStack Neutron. I think we're trying to say, can we pick and choose? Absolutely. You can do one without the other and vice versa. Some of the things that you get when you integrate those, your IP address management, for example, is simplified. You get unified visibility to all your flows because Aviv will provide that, but they're more of layer four and above. On the contrary, you can get it from below. So kind of like the split world, but when you put them together, then you can pretty much look to one central source for all your traffic flows and management from your network perspective. And they kind of like dump the application concerns off to the application team. So there's a kind of nice differentiation of separation concerns that does help. There's ECMP on top, which is nice. If you want to scale out with one IP address across many instances, that is something that I think is pretty unique to Contra. So the ECMP layer is basically like whatever your gateways are configured for. So you're probably looking at a standard like five tuple hash there. But where you want like an Aviv network controller or HAProxy or something, depending on your level of sophistication, is if you want to do like a graceful drain example of like a node or have a specific like health check that says, oh, this is returning a 200 and I will take action if I get something else. ECMP is just blind. It's just like, you know, here's traffic to fire hose where you get much finer grain control and like application understanding to help you manage that. Especially like blue-green deploys, things like that. They're real valuable. So for any application kind of deployment cycle, you do the local development, you do the test and production set up blue-green kind of deployment canary testing and then move it to the production slowly and gracefully. And it can be either for applications or even for load balancers or even for web servers. If you are trying to get off of one web server to another, you can do the graceful migration of slowly doing it, testing it out and because you have the visibility from AV load balancers, you know exactly where it's going wrong. So for example, I'll give you my own living example. I'm in product marketing and I am not an engineer that can go into the weeds. When we were migrating our AV network's website from one web server to another, we had to make sure that it doesn't go down because we just did that last week during Red Hat Summit when we had a press release going out. So we had to make sure that the graceful migration happened and when there were four or four errors from random URLs that I didn't know exist, that I didn't know were existing because those landing pages or those specific URLs were set up before I joined AV more than a year and a half ago. I saw from the dashboard that there was a four or four error. I looked it up. Okay, these are all the four or four errors coming from these clients or these random requests that are coming in. I could immediately set up a redirect from AV console that if a request comes in for this URL, redirect the traffic to this URL. So it was quick, easy. Even for someone in product marketing to do that, it was just easy. Yes. Contrail. Right. So if you go with Contrail for your Layer 2 and 3 network automation, we extend that kind of network automation and application automation through L4 through L7. So you get a complete network automation from Layer 2 to 3 to 4 through 7. Yes. Support for DPDK. Yes. Any other questions? Anything else you wanted to add? Okay. So we are right at the marketplace at Booth 821. So if you're coming out from Sheraton, you can walk through the other exit. We are on the left. Walk by the Booth. If you have any other detailed questions on how Avi works to further extend integration with Contrail, we can show you that we're just open stack. Or even outside of open stack, if you have kind of an on-prem deployment, we can show you how Avi works on an on-prem deployment. And we have cool shirts like OpenStash. And we also have an acronym that goes something like beyond application delivery as a service. I will let you guys figure out how to spell it. I mean how to say it. Load balancers are traditionally called application delivery controllers, but we go beyond application delivery. So we kind of came up with the acronym called beyond application delivery as a service. So we have the t-shirts. We also have the fidget spinners if you're interested in fidget spinners for the kids. So come over to the booth. We can show you more demos if you want. All right. Thank you, everyone.


At Safe Work Australia we work with government, industry and business to try and help and improve the health and safety of all workers and an important part of this is about providing quality data and evidence so that people can understand not only the importance but also the impact of health and safety at work. Each year we report on work related fatalities in Australia and that includes information around the nature and circumstances of the fatalities and as part of this we try and highlight what the most common causes are of those fatalities but also the industries and occupations where they most commonly occur. These statistics not only provide data on all workers that are killed in a work related incident whether that be an employee or a self-employed worker or volunteer it also includes information on bystanders who are killed as a result of someone else's work activity. I think data can be a really powerful tool. The aim really of publishing these statistics is so that leaders, employers, workers, regulators and others can better understand where the greatest risks are and to be able to then use that and share that those learnings to further their commitment to improve safety at the workplace. Well the positive news is that the rate of worker fatalities in Australia has almost halved since 2007. In 2016 the fatality rate in Australia was at its lowest level in the 14 years of data that we have available and I think that provides an indication that the work health and safety laws policies and strategies here in Australia are having a positive impact. But while the the improvement over the last 10 years is certainly pleasing, the latest statistics do show that there were still 182 workers who were killed in work related incidents in Australia in 2016. In 2016 50% of worker fatalities occurred in just two industries, the transport, postal and warehousing industry and the agriculture, forestry and fishing industry. And I think by understanding where the fatalities most commonly occur and also what the main causes of fatal injuries are, it enables us to better focus our efforts to try and ensure that these tragic incidents are avoided in the future. What the data shows is that certainly vehicles are a big factor in worker fatalities. In 2016 more than half of work fatalities involved vehicle in some way. In 2016 the main cause of worker fatalities was vehicle collisions with more than half of those involving a truck. Workers falling from a height was the next most common cause and and almost half of those or just under half of those involved workers falling from a ladder or a roof and then that was followed by workers being hit by a moving object such as a vehicle or machinery. Compiling, sharing and analysing the statistics are an important way in which we try and raise awareness and to provide a national picture of work health and safety outcomes in Australia. I encourage people to share this video and to use the data in it in order to raise awareness but also to help improve the health and safety of workers in their workplaces.


Today, Tuesday, November 17, 2020, the Ministry of Health and Wellness received confirmation of five new cases of COVID-19. This brings a total number of cases diagnosed in country to date to 178. Case number 174 is a one-year-old male from the Viewfort District. Case number 175 is a 13-year-old male from the Choiselle District. Case number 176 is a 31-year-old female from the Grozile District. Case number 177 is a 54-year-old male from the Castries District. Case number 178 is a 44-year-old male from the Grozile District. All of these individuals, after being assessed and tested for COVID-19, were placed in quarantine by health practitioners while awaiting receipts of their test results. Three of these cases were identified through the contact tracing process and an epidemiological link has been established for these three cases. Case number 174 is linked to cases 109 and 165. Case number 175 is linked to cases 109 and 163. Case number 176 is linked to case number 169. As a protocol, the arrangements have been made to place these individuals into care. The Ministry of Health and Wellness is pleased to announce that the reported critical case has recovered from COVID-19 and has been transferred as of yesterday to the Owen King EU Hospital for continued care. This now springs the total number of active cases currently in country to 116. At present, all of the remaining active cases are stable. The Ministry of Health and Wellness be once again remind everyone that we are all susceptible to the virus. However, there are persons who are at greater risk, such as the elderly and those living with chronic and underlying medical conditions. Therefore, we all have to play our part to protect the health and safety of our families, our friends, our colleagues and our neighbours. Let us all continue to take personal responsibility and adhere to the protocols and guidelines for the prevention of the virus. Let us continue to practice the infection prevention and control guidelines that will help to reduce exposure to the virus.  Sanitise frequently touched surfaces often using a bleed solution. Maintain the separation of 6 feet from others, which is about 2 arms length apart. If you are experiencing flu-like symptoms, keep away from others and seek medical care immediately at the closest respiratory clinic. Also, avoid contact with other persons who have flu-like symptoms. The Ministry of Health and Wellness will continue updating you as information becomes available.


For many, intelligence is a high-standing aspect of the one who possesses it. In some cases, they're expected to achieve greatness, while it may seem that intelligent people have it better. Due to their intelligence, awareness, and the pressure of the outside world, there are a few areas where they might struggle. Even with their high intelligence, they are still people who struggle sometimes just like everyone else. Keep watching to find out the difficulties intelligent people struggle with on a daily basis. Number one. Mental and emotional disorders. A 2011 study published in the Frontiers in Evolutionary Neuroscience found a correlation between general anxiety and high IQs. The cause? They posited that individuals with higher IQs had lower concentrations of choline in their white matter. Choline is a compound that helps produce a neurotransmitter, acetylcholine, which helps regulate your mood. Additionally, a study conducted by Ruth Karpinski of Fitzer College and her colleagues showed that intelligent individuals are at higher risk for psychological and physiological overexcitabilities. Her findings showed that out of the group of people they studied, 47% suffered from mental illnesses. The study looked into a high IQ society called Mensa that only accepts people with IQs of 132 or higher. This information was included in an Origins article. Mensa is a care provider that focuses on addiction, mental illness, and others. They dove into what the Mensa study might say about the possible causes and reasons why people with high IQs have a high probability of developing mental illnesses.  According to Origins, overexcidibility can turn into overanalyzation, worry, and rumination that will eventually turn into anxiety or depression. Normally, people with higher IQs are ostracized or pushed to the fringes of society due to the society not being able to understand them. This isolation in turn can cause depression. Finally, due to their high IQs, intelligent people are more self-aware and can know when there's something wrong with them quicker than normal people. Because of this self-awareness, they're more likely to seek medical and mental health to get diagnosed. More so than others. 2. Stress While intelligent people have the ability to synthesize information and understand complex information, they're just as sensitive to stress as many of us. Perhaps even more so than the average person. As mentioned in the previous point, highly intelligent individuals have a reduced concentration of choline in their white matter. Due to the reduced production of acetylcholine, many higher intelligent people are sensitive to stress. Acetylcholine is an important neurotransmitter that regulates your stress. Without enough choline, people can develop anxiety, chronic stress, or depression. Neither of the three are conducive to good brain function or a happy life. If you also take into account the social pressure and scrutiny intelligent individuals are placed under, life for a highly intelligent person may not be as fantastic as you might think. Luckily, choline is found in foods you may already consume, fish, poultry, eggs and nuts. 3. Social burden When you picture a highly intelligent person, you probably picture a Nobel Prize winner or a successful CEO. Unconsciously we hold these individuals to certain standards. But intelligence does not automatically indicate success. Aware of the expectation of others in society, highly intelligent individuals might feel pressured or place undue pressure on themselves. They might take on more than they can handle, which eventually leads to burnout. They may also try to do big things quickly, meaning they pay no attention to the small steps they need to take in order to make those big things happen, which can lead to them failing. Marty Nemko, PhD. A personal coach and educational psychologist wrote in a Psychology Today blog about how intelligent people are perceived in terms of expectations. They're expected to always be intelligent, said Nemko. But even smart people aren't always on. And then, like anyone else, they're more mistake prone. But they and others are particularly hard on themselves because of the disparity between their usual functioning and their error. Nemko continued. Intelligent people are expected to make a big difference in the world. Lest they choose a less ambitious career, they're often denigrated as not living up to their potential. 4.  Most people don't like it when they feel as if others are trying to flaunt their intelligence because it makes them feel inadequate. Although, not all intelligent people flaunt their high IQs. Instead, they like to talk about what they know and try to help others. Having a high IQ doesn't mean that you're smart at everything.  This gets them into trouble sometimes as they may say or do things unintentionally that confuse or hurt other people. 5. Self-esteem tied to their intelligence Another negative side to being intelligent is that due to the outer and inner pressure, many intelligent people end up tying their self-esteem, self-worth and identity to their intelligence and ability to always do things perfectly. In his blog, Nemko explains that due to intelligent people being aware of their own intelligence and how highly regarded it is by others, they tend to get wrapped up in it and only depend on themselves. So they tend to rely too much on their own judgment, Nemko stated. No matter how intelligent a person is, obtaining outside input often leads to better decisions. So they may end up making worse decisions than do somewhat less intelligent people who are aware of their limitations. Most intelligent people's careers and self-esteem are tied to their intelligence, Nemko said. Aging's inevitable cognitive decline tends to especially hurt smart people, practically and psychologically. If you are considered to be one of these highly intelligent people, remember that in the end, we're all human and mistakes are part of our lives. Don't push people away due to pride or arrogance. You might need them later on. These are just a few of the difficulties that intelligent people face in their lives.  Some might just seem like they are. More likely than not, they're worrying more than trying to show off. Do you agree with the difficulties mentioned here? Let us know in the comments and don't forget to check out our YouTube channel for more.


Alright, thanks for sticking around until the end of the day. My name is Karthik. Can you hear me in the back? Yes. So I'm with the Berkeley Institute for Data Science, and I'm also involved with a lot of different open source projects. I lead a large open source project called R Open Sci. The thing I want to talk to you today is how to get credit for any research software that you might develop. So this is my first time at Fostem. I actually thought this was a pretty small conference and that I would have to convince you that software is important. I don't really have to do that, but I'm going to do it anyway. So the thing that's always striking to me as an academic is that software is so prevalent in every academic endeavor. It's not just heavily computational fields like astrophysics or bioinformatics, but even many of the humanities that you would think are not computational are computational these days. And it's hard for me to actually capture this better than, say, Guile Veracou, who is the lead for Scikit Learn, is that software helps us make predictions from models. It helps us run experiments. It helps us derive insight from data. And this is just universally true in a lot of different fields. And this is not just anecdotal. So I have some colleagues that have done surveys in the UK and the US to try and find out how much research software people use. And this is not just things like Microsoft Excel and Microsoft Word, but software designed for research. And it turns out that more than 90% of people rely on these types of software. And when asked what happened to their research if the software disappeared, more than 63% of them said they just have to stop doing what they're doing. So research software is really quite critical for a lot of different fields. And more and more I am seeing academics spend a lot of time taking their code and packaging that into software. You see everyone pulling together a package these days. And it's really interesting that currently the skills that we require to thrive in academia are not actually all that different from being in industry. And funnily enough, the person that said this, Jake VanderPlas, friend of mine, was an academic and now works at Google. But luckily he's still just doing whatever open source he used to do before. He's just getting paid a lot more money to do it. But the challenge with doing software in academia is that it's not considered research and it's very hard to get credit for academic software work. And there's a reason why we really don't know how to give credit to software, which is the biggest problem. Very simple things like we really don't even know how to cite software. So it's kind of all over the place. Sometimes people cite a paper. Sometimes people cite the entire language to reference a single package. And this is not just true of tiny journals, even big journals like Nature and Science. People just casually mention software. They don't quite cite it, which means that you will never be able to track down the actual version that anybody used if you're ever trying to think about reproducibility. And then there's a big consequence to all of this. If we are not going to get credit for our software, we're not going to do a very good job of it. It's not going to be sustainable. It's not going to be collaborative.  So we need to really find a way to make software scholarship and give people credit for that. And that's what my talk is all about. And a handful of us decided we need to do something about this. And so when you think about software and citation, it's just a mess of different types of challenges. There are very few things that are technical. It's mostly cultural. We're not quite ready to do this. But for example, there's not an easy way to cite software because we haven't quite agreed upon writing papers about software or directly citing the software itself. Software citations not being allowed is a weird cultural thing. It's not usually indexed by the Bain counters. And until recently, people didn't actually peer review software. And that's something that I've been involved in for a handful of years now. And even though software has dependencies, we don't actually have a clear way of saying what software is connected to what other software. And so just a quick reminder about why we cite things. We're trying to give credit. We are trying to make it clear to everyone that we've done our homework, make sure that we're not stealing from other people. But at least with software, the biggest thing that we're trying to do is we give proper credit to someone who's building that software. And so how do we go about recognizing software for academics? So there's two possible ways. One is we could try to do things in ways that academics are already quite familiar with. We do research. We write papers. We get the papers published in the best journal possible. People cite our papers eventually. The citations that add up, we get credit. Or we could try and think of something new and interesting instead of doing the same old boring nonsense. So because software has dependencies, there's more interesting things that you can do and just go beyond that very simple one-dimensional credit model. So if you imagine this hypothetical example of Arfan Smith who wrote a paper and then he references a couple of his old papers because he's building upon previous work. He references a couple of large data sets and then he references two critical pieces of software that he used, in this case, AstroPy and Scikit-learn. But because of dependency trees, we can tell that these two depend upon NumPy and SciPy. So there should be a way to automatically assign credit to software without having to cite every single piece of software. But we're not very good at agreeing upon any particular standards and trying to get a large group of people to agree to a big piece of change is very, very hard. So we'd have to get buying from individual authors, editors, then move on to whole communities and societies and then get the journals on board and that's really not going to happen. And so the alternate option is just writing papers about software, which is pretty easy to do and it's not a bad thing because a paper can be something that you can just easily cite. We don't really have to create any new infrastructure and then if you are writing software that is important to your community, the best way to bring this to the attention of people in your community is just to publish it in a journal. People read it. There's a challenge, though, trying to get a software paper into an existing journal which is that if you've already done a full research paper, writing another software paper is really painful. You're going to copy all of the documentation that you've already extensively written as part of your software into a paper. Most journals don't publish software papers and for those of you that contribute to open source, if you join a project that already exists, it's very likely you'll never get credit for that work because they already published one canonical paper for that work. That's a common problem for people that joined the Jupiter team. Everyone cites something that's quite old at this point. So we've come to realize that trying to change the system is really hard and so we are going to have to stick with what exists and just hack something around that. So my colleague, Arfan Smith, who founded the Journal of Open Source Software, several of us started talking a few years ago and said, can we create a new type of journal that makes it easy to publish papers about software without making it very difficult? And so we created JOS, Journal of Open Source Software. It is entirely free, open access, it costs nothing to publish, and we created a new system that is very developer friendly. And by developer friendly, I mean that if you would like to get a publication for your software, assuming you have followed all the best practices, you've written good documentation, you have tests, you have clear installation instructions, you've designed a usable piece of software, you've got a good open source license, then we expect that it should take you no more than an hour to write a paper. And the JOS paper is actually fairly simple. It's often no more than two pages long. It's a very, very high level description of what your software does to someone who's not an expert in your field. We're really looking for you to cite who funded you, major references that influenced you, and we really do not want you to put any results in this paper. It's just a simple, citable object for your paper. And we tried to be as conventional as possible in the scholarly space, so we didn't throw anybody off. And this is what the form looks like. Has anyone submitted a paper using Manuscript Central? A handful of you. You know how painful that is. Here, all we need is your name, your version control repository, and if you have an editor in mind. That's really it. You can even skip the title and the description because we already have that as part of your paper which you write in Markdown and then put it in the same repository as your project. And the thing that we built is a robot which is basically a Ruby bot that runs on Heroku and listens for every single activity on a GitHub issue. And this bot, which is the one in the middle, can talk to GitHub and it can talk to a bunch of different services. We named it Weedon because the journal of open-source software is Joss Weedon for sci-fi fans. And as soon as a paper goes into the review queue, Weedon steps in and says, hello, I'm a bot. I'm here to help you. If you'd like to know all the commands that I can do, just type in atWeedon commands and Weedon will tell you everything it can do. It immediately starts to identify what language it is and starts to tag the language of that particular submission. And then Weedon is really nice because it gives different powers to different people. So if you're an editor, you can assign reviewers. I can just say, assign Matayush to be a reviewer and then it'll assign him as a reviewer. I can, if I'm an associate editor, I can assign someone else as an editor and I can also just start a review which just creates a giant checklist for the reviewer to work through. It also gives powers to the authors and the reviewers. So at any point in time, they can say, Weedon, generate a PDF. So it goes through the markdown, goes through the references, generates a beautiful PDF. You can look at it. If the formatting is bad, keep adding more commits, generate another PDF. It will check references. It will go crawl all the DOIs and let you know when something is broken. And then if you've got superpowers as an associate editor, you can say, Weedon, accept this paper and then it will go deposit all the metadata, archive the paper. And right before that, you also archive the software itself. And in the end, we create a PDF that looks like a standard PDF to most academics, which is good because you don't want to confuse them by showing them a software paper. So this is a paper that was recently published about the tidyverse. And when you go to the JOS page, you can see the review. You can download a PDF. And you can see all the orchids for all the authors. So we've been running the journal for more than three years now. We wrote a paper right after the first year describing how the journal works. Some of these statistics are outdated, but the trends also hold. We tend to get a lot of submissions that are Python packages and R packages. And most of our submissions come from the US or the UK. We're getting more submissions now. And we're growing quite a bit. We've published almost 700 papers. We published 30-ish papers a month. We've got a lot of editors and we're constantly growing. And in many ways, even though we created a journal, we really just created another open-source project. So you imagine in an open-source project you get users who get very excited and at some point they start contributing and then they end up becoming maintainers. So you can then step away and hand this off to someone else. It works similarly for us too. We get people that submit to us and because our reviews are 100% completely open and public, they get to see how the whole process works. They want to come back and they want to review. And then at some point, if someone reviews too much for us, we just make them an editor. Lastly, I want to give you a few insights that we've learned running JOS over all of these years. So one of the things that we've done is we've tried to make JOS, even though it's experimental and interesting, seem very much part of the scholarly infrastructure. So we don't have our own login system. We use Orkids, which are researcher identifiers. As soon as we accept your paper, we archive it, all the metadata with Crossref. We archive the paper and the reviews with Portico. And then just about a couple of months ago, JOS papers started getting indexed by Google Scholar. We're still trying to work with Scopus. We love best practices. So all papers are open access. All the authors have complete copyright control over everything. Our governance strategy is fully open. Our business model is that we don't have a business model. It costs us very little to publish any paper. And then even though we're doing all of this, we're doing a pretty thorough job reviewing your software. So we're giving you a citation for a very short paper. But along the way, we're checking to make sure you have a good license, your software functions as intended. If you claim any performance improvements, somebody will go test that. And then we go through a pretty big checklist. The process is quite fun for authors. So we just heard a talk about how E-Life is trying to make things open and transparent. JOS doesn't really reject papers. Our goal is not to reject papers so we can inflate our... I forget what we're trying to inflate. Our acceptance rate. So we always do a desk reject if the software is not fully complete or not appropriate or it's not a research software. But once you get past that point, we want to help you succeed. And the goal post is very clear.   We try to leverage the best parts of open source. So we figure developers are already on GitHub. The journal lives on GitHub and the bot acts on GitHub. And then we try to automate things that are very tedious and boring, and that's what Weedon really does. So if any of this seems appealing to you and you would like to submit to JOS, please submit a paper. If you have a software package. And if you have expertise in any open source language, please sign up to be a reviewer. And I'm happy to take any questions. Thank you. Yeah. So we have a potential solution to this, which is that... Oh, sorry, I'll repeat the question. So the challenge with contributing to an existing open source is that there's already old publication and you will not get credit. So we would like to encourage people to submit new papers when the software has made a major milestone leap. So at that point, everybody that contributed in that previous iteration will come on board. So that is a way we can give other people credit. Yeah, thank you for that comment. It does work, but the challenge with traditional publishing is that you have to have novelty. So it's always hard to get a publication that adds to an existing software. But if that works, that's great. Oh, yeah. Okay. So we work through a checklist, and that checklist is very public. So we're not really passing judgment on quality, but we want to make sure the documentation is easy to understand the software actually functions. So reviewers have to step through every single function and every single example to make sure it actually works. And so you end up with software that is not broken, that is not difficult to install in a different platform, actually has a license. So we just make sure it meets a whole bunch of benchmarks that are signals of a good usable piece of software. So we're not doing a very deep code review. Yeah. Right. And if someone else has done a much deeper code review, we will actually rely upon that review as well. So reviewers are transferable into JOS. Good question. So this is a very difficult question. I'll repeat the question. How small can a piece of software be to get into JOS? This is the common topic of discussion among the editors. So we have a cutoff that you cannot publish a minor utility. It has to be slightly substantial in what it does. And Weedon actually does a quick scan of the software. And then if there's any doubt, we will have a discussion among the editors to get consensus. So somebody who's an expert in the field will come in and say, oh, this actually is a very trivial implementation of like one single method. And then we reject that. We do actually. So how do we deal with papers from languages that are not very common like Haskell? So right now we don't get any as far as I know, but we struggle with some languages like Julia where we don't have enough reviewers. So as soon as we know that this is a problem, we just try and reach out to more people to sign up. And so our reviewer sign up forum tries to get expertise on languages. And every few months or so, the editorial team will decide that we are lacking editors in a certain area and then go reach out to people to come join the board. So if you know someone who's an expert at Haskell, maybe you that wants to help out, feel free to reach out. Excellent question. I don't know if it is, but if you want to publish here, you have to be open source. That's another way. But overall, I think it's against academic spirit to not be open source. So especially if it's publicly funded research, why on earth would you create proprietary software? So unless someone can come up with a good reason, I don't have one. Oh, that's totally fine. Our review process happens on GitHub, but your code can sit in any version control repository of any kind. Let me see if I follow your question. How do you actually cite other methods? It's tricky. So we don't require a lot of citations as part of JOS because we are only looking for a paper that is a very high level description. So if you want to cite a fundamental paper that describes random forest, you can put that in your references. It's totally fine. But we're not looking for a very exhaustive list of references. People usually put maybe five to ten references in their software publication. Wonderful question. How long is the review process? I've seen one that has happened in a couple of days, and I've seen one that's taken many months. It's all up to how fast we can work with the authors. So for example, you submit something and I say, you're doing a test that's missing. And then you tell me, I just started teaching this semester. I have zero free time. I'm going to come back to this next semester. That happens quite frequently. But if a software is pretty well used, pretty feature complete, sometimes we don't really have much to point out. And the few things we point out, people will immediately commit, and then we just go accept and then it's done. Good question. So we haven't encountered that problem yet. How do we deal with plagiarism? Especially I mean people stealing other people's code. So we have not really done much about that yet. I'm sure we can build in more functionality into the bot to actually try to detect some of this. But so far we haven't come up with this. People do have to explain what they've done and how is this different from something else. So you cannot just make an incremental change to an existing piece of software and say, this is my JOS publication.  And the editor who's handling that paper has to go verify that. But that's actually a great suggestion. And one of the things we're doing is we're making our bot smarter and two people are now working full-time on the bot. So that's something that we could add for the bot to look into. Oh, yeah. So great questions. So how do we integrate references back to package managers? It's all up to the authors. So as soon as a paper is accepted, we tell, for example, here's a submission that was accepted. And the very last thing we tell the authors is, congratulations, your paper is now accepted. Please add this information to the read me and the citation. So if you're on CRAN, you add this back to the citation file, same thing with PyPy. So it's up to you to advertise everything back if you don't have an automatic way to do this. Thank you. Thank you very much.


Jean-Yves, who works for the Water and Sanitation Department. Change of subject, complete change of subject. A bit random this, but it's much more fun that way. And we're getting serious. We brought stuff with us now to show you. I'm not mucking around anymore. Good afternoon. I'm here to share with you a new way of thinking regarding aging water bubbles. So it's called the Niger Refresh Project, paradigm change. Actually, to be honest, since we talk about bow holes, we hesitate a lot to call it boring in debt, but we have thought that you just escaped running away for coffee, so we kept paradigm. So it's not easy for me to pronounce it paradigm. Okay, so as you know, water is one of the main health determinants, and it's a necessity for every single MSF intervention. So fortunately, most of the time, or very frequently, we find this water as a groundwater resource. So we pump this water from bow holes. So for those who are not accustomed with bow holes, imagine that you have geological formation acting as a porous media. So you have a rain, water falls on the ground, by gravity infiltrates all the pores of the ground until it meets the bedrock and then starts saturating all the pores and you have your water table. Now you drill a long hole, you install a long pipe that we call casing, and at the bottom you have a pipe with holes that we call slotted casing, and then you have your bow holes. And the water will enter by the slots and will balance inside and outside of the pipe. So if you pump, water will be attracted all around to refill the bow holes. That's the process.  So it's quite a boring video that you will get. Actually we experimented and we went in many MSF contexts and so it's borehole that supply hospitals and population and it was not so boring. So here you have Afghanistan, for example. It's corroded steel casing, possibly collapsing after a few years. Afghanistan again. So it's a calcium deposit, little by little you have the slots which are clocked and decreasing yield. Haiti Tabar Hospital, famous. So 56 meters, you have organic growing materials. Bokina Faso, borehole in the middle of a village. So you have at the school break the kids coming and throw stones in the borehole. So it's filled until 16 meters. Another borehole in Bokina, so it's full of sand. So when you pump, the sand is lifted and the pump damaged. Niger, Manganese oxide deposit until you have the slots completely clocked. No more yield, abandoned well. Clay with iron oxide deposit. Bacteria growing until it's completely clocked as well. Abandoned. Tubidity. Growing roots. Alive worms, a lot of them there. And then broken casing. So you see that everywhere we go, we face aging boreholes. So normally in such a situation, people go for a new borehole. They pay 15,000 euros for one borehole and they proceed. First, we try a new approach based on diagnosis and based on regeneration of performances. The equipment that we use are hanging tools in the boreholes. Like here we have a hanging camera and we can follow the investigation in the car on the screen. Inside the car you have first the winch where you can operate until 150 meters deep. And we have equipment to, we record data and we record videos. We have also data logging equipment. We record parameters that we transform into Excel graphs. Here for example you have a zoom between 40 and 80 meters deep. With the camera we saw that we have two slotted casing. The first one supplies 14% of the total yield and the second one supplies 86% of the total yield. And here you see that there is no water at all coming from this slotted casing. So you should refer to the video. You should refer to the geology. You should refer to the Driller logbook. All this information that helps you to decide if we proceed to a regeneration process or it's just maybe a borehole badly constructed and you have no water behind the slots. So just to tell you that the technical equipment that we have is only a part of this huge investigation puzzle. We should be concerned with all these points. So to take two case studies, the first one is Bokinafaso-Unde, recent borehole, 70 meters deep, 40,000 euros abandoned for blockage at 35 meters. So we proceed with the first inspection. 9 meters we see the casing. 20 meters we see the water level with a piece of wood. 35 meters we see bags of cement. So the workers that came to complete the surrounding wall, they thrown their rubbish in the borehole and they blocked the borehole. So we came with a custom made and very cheap device for airless pumping. So we blow compressed air and we pump water, mud, sand, gravel and we succeed to unblock the borehole and recover until 67 meters. So here before you had the wood now you remain with the water level. You had the bags of cement. It's clear. We have dirty slotted casing and we have the main stone that fell in the bottom. So we still remain with a dirty borehole. So we decided to clean this borehole with appropriate cleaning agent. Here it's acid based. We have custom made toothbrush for borehole for scrubbing activities and we proceed with rinsing and flushing to complete the work. So we have a small video of the first well that we tried because we were quite happy. When we flushed the well to finish to complete the work. So it's really happy to see that. Okay, we can stop. I don't lose minutes, huh? It's not finished. Okay.  Now you have a very clean casing.  Now you have a very clean slotted casing. So a success. A second case study. Boquina Faso again. Borehole abandoned because it's filled with sand. Investigation, 10 meters of the casing. 35 meters. We see a non-screwed casing. That's where the sand enters inside the borehole. So the casing and at the end you have the accumulated sand. So we came back with our airlift pumping device. We remove all the sand from the borehole and we recovered the bore until 51 meters. But we still remain with our openings, permanent opening and the sand still enters the borehole.  We add a rubber seal. And we insert in the borehole and then we patch the borehole at 35 meters. Full-rate pumping, no more sand. Success again. So in Niger we had two years' field activities. 40 boreholes diagnosed. 12 boreholes regenerated. In terms of cost, we have two visions. The one we choose for diagnosis, we invest 80,000 euros and we have a workshop ready to be operated during 10 years. Or you just outsource and you pay 2,500 euros or 3,000 euros per borehole. Regeneration, we always remain under 3,000 boreholes so far. Sometimes it's much lower according to the treatment. And many constraints, security and broken engine that delayed work. So we believe that we increase the speed of intervention. The efficiency also with a lower cost. We reuse rather than discard. Important, we have overall understanding of the hydrogeological context. For example in Niger, you have a multi-layer supplying aquifer. One of these layers has a high concentration of fluoride and surrounding population, a part of it has dental fluorosis. So with our workshop we are able to exactly to study this situation and to really investigate and to define exactly what layer is contaminant. So we believe we can come back with the Ministry of Water on the drill and make recommendations on their way to construct boreholes. So for us we believe it's a high impact in terms of public health. Oh, I'm sorry. Hydrogeology is a profession so it's not easy to access. We have a high expat turnover with a basic Watson knowledge. Difficult to hand over to national actors and we are not always possible. So until now we have an emergency camera kit, hand carried, 70 kgs. It just came back from Malawi. We have in development a full investigation kit. So lighter but very mobile, 100 kilos for people. We want to start after some of the study on fluoride in Nigeria and deploy early next year in Zimbabwe for cholera and typhoid recurrent outbreak. And here we believe really that this workshop is really appropriate for borehole maintenance, regeneration, rehabilitation. But it's also for us an open door for deep study and we believe we can have a huge potential in terms of impact on public health that we want to take advantage of. But then we still remain with our before mentioned constraint and then we consider for the moment if we keep it internal or if we would create an external service provider as a technical interface. So here is the small emergency camera. So actually it's just a small camera, very basic. And we have, if I can break it, the video recorder so we can go anywhere to make some videos quickly for the first phase of emergency. That's all. So thanks to all these people that helped the project to be alive. And thanks to you to listen to them. Thank you very much. Technical questions and please state your name, organization and stand up if possible because it's easy to see you. My name's Kirillian from the Institute of Topical Medicine and Antwerp. This doesn't mean to be a negative question but what do you then do afterwards to make sure the kids aren't throwing stones back into the well that people aren't going to come and fix it and put more cement in? Is there sort of a way to follow up and I guess maintain them? But I guess, I mean in every village there in Burkina you have a chief of the Ministry of Water so you're supposed to have a borehole with a lid with bolts and to have a surrounding wall with a closed door. So this didn't exist. So I don't know what happened with this responsible because we were with the main director from the capital so possibly he got some serious problems. The point to make is perhaps the collaboration with the local authorities, the local ministry of water. We always collaborate with the Ministry of Water because here we touch boreholes which doesn't belong to the authorities so we are not allowed to touch these boreholes. We need agreements with them so that's what we proceed all the time. Perhaps on a local level you could comment on the relationship with the local population who benefit from the borehole and the relationship developed with them some kind of education surrounding the... Yeah, possibly yes. But anyway, normally in terms of borehole protection all boreholes should be well closed and protected otherwise it would get contamination very soon. Time for one more question. So I'm just going to ask a question about if there's any monitoring of the quality of the water so there's been problems reported with arsenic and salamization around the world. Do you monitor the quality of the water that's coming out? For us, as I said, the investigation is like a big puzzle. So to monitor or to follow the water quality is really a pillar of the project as well. So we cannot just go and take measurements or videos. The quality of water is one of the main issues. For example, in Niger we have an agreement with the Ministry of Water. So we have someone from the Ministry always with us on the field and they keep the heart of the Ministry when we open the borehole and we take samples that we bring in the National Lab and they provide the analysis and we provide the consumable. So it's a good win-win situation. So we really collaborate with the Ministry of Water. It's a part of the project. Thank you very much.


Hey there, Psych2Goers. Welcome back to another Psych2Go video. Emotional maturity is important when it comes to maintaining healthy relationships. Maturity has little to do with your age, but how you act and think. There are a lot of people who are young and mature, and people who are mature think and act in a certain way. Want to find out whether you're emotionally mature? Here are six things emotionally mature people do. One, you take responsibility for your actions. Everyone makes mistakes now and then. When you realize you've made a mistake, are you willing to admit it? Or do you look to blame it on others? As an emotionally mature person, you're always willing to take on the responsibility of your actions. You readily take accountability for the consequences your actions may have. Two, you put yourself in other's shoes. Are you able to see a situation from others' perspectives and understand how the other person is feeling? When you're emotionally mature, you're able to be empathetic towards others. To you, being able to do so not only helps others through their time of need, but also gives you the opportunity to support someone and further develop your interpersonal skills. Three, you're able to show your vulnerability and ask for help when needed. When you're in need of help, are you able to recognize it and ask for help? Accessing help or simply asking for it has been stigmatized as a sign of weakness. However, it's an indicator of strength and maturity. Developing the skill of acknowledging when you're in need of help requires practice, but it's extremely rewarding in the long run. Or you express your gratitude even during difficult times. Being able to reflect on your own personal situations and those of others and express gratitude is a sign of maturity and humbleness. Despite the circumstances you may currently face, you're able to see the good in the bad. You know that sometimes you need to see the bad side of things in order to have more appreciation for the good side of things. Expressing gratitude is a great way to build stronger relationships and deal with adversity. Five, you're open to learning new things. Are you always curious and inclined to learn new things? As someone who is emotionally mature, you appreciate the diversity in different subject matters and show respect to different opinions while forming your own. Learning new things is extremely beneficial to living a meaningful and well-connected life with those around you. And six, you think before you react to a situation. You often pause to think the situation through, considering all elements of the matter prior to reacting out of immediate feelings. This pause gives you the opportunity to understand the feelings and points of view from both sides. Excelling at this skill requires much practice. Although, when used efficiently, it can lead to more positive outcomes. Do you relate to any of the things mentioned in this video? Or do you know anyone who is emotionally mature or show signs of emotional maturity? Tell us which signs or signs you found most helpful and why in the comments below. Don't forget to share this video with someone who might benefit from it. Click on the subscribe button for more videos related to psychology and mental health. As always, thanks for watching and we'll see you in our next video.


My name is Melinda Desri. I'm a French archaeologist. My principal studies deal with medieval castles in the center of France. Today, I will talk about the castle of Gia. First, I will shortly present the castle in its octial two-stick landscape. Second, I will show you the recent discoveries made by the archaeologists and how these discoveries changed the understanding of the site. And finally, I will briefly speak about challenges concerning presentation of the scientific results to a wider public. The medieval castle of Gia is a well-conserved monument located nearby the Loire River in the western part of France. But unfortunately, it is not included in the Loire Valley UNESCO Label perimeter, such as other famous castles like Chambord or Chenonceau. It's possibly because Gia was not built during the first French Renaissance, but at the end of the 15th century, just before the French royalty returned with Italian artists after the Italian wars. Moreover, its walls are made of bricks, a material which is rarely used in the later Renaissance castles of the Loire Valley, which are most of time built of yellow to white limestone. Because of its location, very close to famous castle of the Renaissance and because of its early time of construction at the end of the 15th century, the castle of Gia occupies a special place in this historical landscape. Until recent archaeological and historical increase, the context of edification of the castle in the late Middle Ages and its earlier medieval origins were unknown and dealt more with imagination than with scientific knowledge. Rescue excavations started in 2011 when the museum inside the castle was going to be restored. At the western part of the hillside was found a continuity of the castle of the 15th century. It was composed of several rooms. Here you can see the aerial view of the excavation. And here we have the detail of the chimney and of the floor made of permanent. In this part, we found the largest room of the castle. It had a representative function. The space was used for rich reception dinners for drinking and feast and so on. At the same time we did the rescue archaeology, we also analyzed the process of the building construction of the actual castle by using dendrochronology. It allowed us to understand that the castle was built from west to east in a very short time. It took only 11 to 12 years to be constructed. This short time might be explained by the fact that the materials were provided from the natural resources that was owned by royalty or that the royalty could easily find in surroundings. These materials are the clay for the bricks, of course, but also also the wood and expensive resource, which involved a very strict management of the nature. We suppose that the construction of the castle of Jain required around 900 logs of oak trees. These trees were cut from the forest, lying only few kilometers around Jain. However, some trees required special resources management. This may be the case for example of this huge beam decorated with a little bear, having one meter of diameter, which could have been specially searched and selected. Also, limestones used for the limitation of windows and doors have been chosen and carried by the Loire River from the territory of central France. So we can ask the following question. Why such a royal residence in this location? Jain is located exactly at the limits between the Orléans du Chez and the Burgundies du Chez areas. At the end of the 15th century, several lords from Burgundy and Orléans did not recognize the authority of Louis XI, the King of France. The castle was built after the end of the quarrel, after the death of Jean-Charles de Téméraire, the Duke of Burgundy. It was constricted by Anne de France and Pierre de Bourbon, who took the head of the kingdom during the sickness of Louis XI. Building a royal castle in this place, in this political complex, signified that French royalty kept an eye on this ancient Burgundy territories. So the place of Jain reached the kingdom of France at the end of the 15th century with the construction of the castle of Jain. But what was the place before? From the archaeological point of view, we can see that Anne de France intentionally didn't care about constriction made in preceding periods. She almost totally erased previous building. However, she didn't totally erase the first stages of the indoor floors of a locked tower that we found under the destroyed wings of the castle of Anne de France. This locked tower could certainly have been owned by Burgundy lords and might have looked like this one. Its indoor floors contain, for example, several fireplaces and storage pits. Micromorphology's analysis made on fireplaces told us about the activities done inside the building during the 10th century. It allowed us to conclude that not one, but several types of activity took place in the same fireplaces. And each activity has been performed during different duration periods. These activities were, for example, activities of cooking, represented, of course, by the fights of animal bones, but also extents. Metallurgical activity were mostly represented by slag and other forging macroscopic residue. Forging activities probably concerned, for example, fixing iron house shoes or fixing other zinc and copper objects. These clues along with other clues concerning food habits indicate the high status of inhabitants able to use and control also metal resources. Nearby this tower, a contemporary settlement composed of three different houses was excavated inside the actual castle. The micro-analysis of floors told us about the lifestyle inside these houses made of clay and wood. The activities within this area were also dedicated to cooking and in less extension to crafting the bones. The floor analysis gave us also some clues about the environment of these buildings. The animal husbandry was identified by their copper lights, goats, sheep, and also young pigs. Different seeds were identified and analyzed, like strawberries, grapes, and so on. That let us know about the farming landscape around. Here you can see paper seed, which were found in one piece. That kind of finding is quite exceptional in the Western European context of Middle Ages, because the paper came at that historical period from India. And this plant was as precious as money. It was rarely eaten, but in the case of Jien, we could assume it was eaten because it was found near waste of food. The presence of paper, as well as the presence of food, composed mainly of wild animal species, like bear, deer, wild boar, peacock, or birds, allowed us to conclude to the high status of inhabitants living in these houses. We suppose that people who lived there belonged to the same social group that those living in the tower, even if housing, are not the same. Now that we have in mind information about the forgotten medieval landscape of Jien, the historical one with the significant construction of the Royal Castle at the end of the 15th century and the previous Burgundy Castle of the beginning of the 10th century, we can ask the next question. How could we transfer in simple and not simplified way this knowledge to a wider public? Unfortunately, we have to underline that often archaeological reserves are not presented to visitors, which is the case for many historical places. In France, we can observe that even if research is done, it is barely spread to a wider audience than to scientists, then to themselves, especially when a study has been done on edifications of building. Here, for example, we can see another old part of the castle of Jien. Also, the tower has been constructed in five different stages. Visitor does not have this information available because of the new restoration. It is like we would consider that what is still standing does not need to be shown and explained. We can say the same thing for the archaeological excavation made beside the castle, which is now totally covered by tree plantations. It is true that sometimes a few medieval artefacts here coming from the excavation of Jien are presented in the exhibition. However, collection presented are often reduced to poor set of artefacts, such as broken medieval pottery or rusting nails. It is not enough, and it does not really help to promote the richness of the medieval civilization. Another thing is that the collection of the museum located inside the castle of Jien is totally disconnected from the history of the site. It is collection of hunting over the age. However, the modern 3D restitution helps us to imagine what was the site behind historical cliché and how it has evolved. You have seen one of these theoretical scenes of Jien during this presentation. Virtualization of scenes based on scientific knowledge were recently proposed, for example, for the visit of some castles in the Loire Valley, like the castle of Jien. However, this visit experience must be extended to archaeological excavation themselves by using, for example, immersive headsets to help people to understand what they can't see anymore and to open their eyes to what they would never have suspected at all. It helps people to reconnect themselves to lost historical landscapes and lost environments. Nowadays, the challenge is that we archaeologists have to do these proposals to take a risk, even if sometimes, information are not complete. The archaeologists and researchers have to continue to ask and claim for an extended refund of their knowledge and to take part in this action to propose to people the hidden past of castle sites. Thank you for your attention.


Alrighty, I have a construction update for you guys today, some really exciting things, sorry if my voice sounds off, just had a rough day. But nonetheless, some stuff is going on at Canada's Wonderland, so construction is definitely picked up at the restaurant, so here you can see the roof is starting to go up by timber kits, and the sides of the building are well in their way, as well as the stonework for the landscaping, the path work is being installed as well. There was a bit of a kerfuffle going on up there, but I'm not going to focus on that just because it's not really for us to watch, but yeah, I caught that on the drones, that was quite interesting. But nonetheless, the restaurant and splash work seems to be the only areas of question right now, and there is still some weird activity going in and around action, sorry, action theater, and nothing new in the forest still, but again, very skeptical of what it could possibly be, just because usually we start knowing about attractions, as I said in the previous video, so us not hearing anything quite yet definitely doesn't sound promising. But yeah, the buildings and splash works are very confusing to me, again, it's just there's a lot of wood still too that hasn't been installed, but the restaurant is also really weird. So if you look really closely, it's got a lot of small rooms in the restaurant. So the building itself, I was expecting a very open design with very long tables, similar to the other Harmony Halls, but this one's got tiny rooms like almost like throughout the building, so that's really interesting. I don't know how that's going to look like it's going to be some sort of like ghost kitchen kind of concept where you can order different menus in one building, and then the downstairs is going to be the eating area, the sitting area, because there's a staircase that leads down. So it's very interesting how this is going to work, Wonderland's been very silent on the restaurant, I would have thought we would have had some sort of renderings by now, and I do know Wonderland has the renderings, trust me, I know that they have the renderings, and some employees have seen them, but yeah, not much else going on in the park, Extreme Skyflyer was getting ready to open, it was testing all day, and nothing much besides that. We got to wait for the Whitewater Canyon path to open to get any more juicy details, but definitely keep your eye out on Dinosaurs Alive, and I believe that the rides that were operating One Train could very well be operating Two Trains this weekend, and if it's not this weekend it will be next weekend, the trains are being assembled and put back onto the track, so that's exciting. So number one train operations anymore, but yeah I think that's it, I guess I'll leave the footage for you guys to watch as they build the restaurant if you want to watch the entire time that I stayed up in the air, but yeah thanks so much for watching this video and supporting the channel, and yeah see you guys in the next video or see you this weekend, if you see me at the park or Craig at the park definitely stop by and say hey, have a good one guys, bye.