You guys know I like to do museum tours when I am traveling from time to time, but since nobody's going anywhere for the foreseeable future I thought it would be a good opportunity to revisit a past museum tour I did a couple of years ago. Stuff that I recorded and still haven't shared with you guys. Hello everyone and welcome to The Vintage Space. If you're a regular viewer, welcome back. If any of you out there have read my new book, Fighting for Space, or if you've heard me talk about it anywhere, you'll know that I'm mildly obsessed with Jackie Cochran, the main aviatrix in the book. If you haven't heard of her, here's the Coles notes. Born in Florida in 1906, she had an exceedingly complicated childhood that she hid during her lifetime under cover of her orphan origin story. She moved to New York City as a beautician in 1929 and three years later on a bet with her new beau, Floyd Odom, learned to fly. She got her license in three weeks and within weeks was making headlines. She left the beauty industry to fly full-time and she racked up awards and firsts, including first woman to fly faster than sound in 1953. When she died in 1980, she held more speed, distance, and altitude records than any other pilot, male or female. On past visits to the Air and Space Museum in Washington DC, I've stepped closely to the space displays. I mean, they've got Apollo 11, Gemini 4, Friendship 7, a full Apollo Soyuz mock-up of V2 next to a Skylab mock-up. There's so much, but that last trip about two and a half years ago was all about aviation and there's so much good stuff. But getting more and more into Jackie's story, I decided last time I was there to track down some of the trophies with her name on them because her stunning career came with a lot of hardware. Honestly, I'd intended to do this as a teaser before the book came out, but things kind of got away from me. So let's go on a mini Air and Space Museum tour of Jackie's hardware now. And just a heads up, this was before I got the fancy new iPhone I used to record these videos in 4K and 60fps. Not to mention, cases are very reflective, so pardon the quality. The Bendix Trophy was an exciting one for Jackie, so it was an exciting one for me to find. In the 1930s, the Bendix Transcontinental Air Race was THE national air race. Sponsored by Vincent Bendix, it was a race from Burbank, California to Cleveland, Ohio that sought to pioneer new developments in aviation, meaning pilots flying in the race had to show their medal against experimental planes. It was traditionally an all-male race, so of course Jackie, who never wanted to be the best female pilot, but the best pilot, full stop, fought to open it to women. Her efforts, along with Amelia Earhart and a handful of other petitioning women pilots, were successful, and in 1935 it became a mixed race, though the women were judged in a separate category. Jackie didn't like that, but she flew nonetheless. She was forced to withdraw that year, the full story is in Fighting for Space, but that didn't deter her, winning the Bendix became her white whale. She entered again in 1937, the lone female entrant this time. Though she didn't win, she did win the women's division by default, which she wasn't thrilled about. I can tell she wasn't thrilled because she never talked about it at length in any interviews and left it out of her memoirs. If she didn't want to be the standout woman, she definitely wouldn't have been overly thrilled over winning a trophy for being the lone woman in a race. So after winning this trophy, she was still in hot pursuit of the big prize, the actual Bendix trophy. She sunk a ton of energy and money into the 1938 race, getting her hands on a revolutionary Seversky P35. This plane had two novel features, retractable landing gear to make the plane more aerodynamic in flight, and fuel tanks in the wings so it could fly further on a full load. Jackie knew these two features would give her a serious edge in the race, so arranged with Seversky to get herself a brand new plane just for the Bendix. The race was an exciting one. She'd worked out all the details of a perfect flight for fuel efficiency and speed, and figured she'd need to fly at about 16,000 feet at a nearly full throttle to get the most from her engine. But that's higher than humans can survive. Cockpits weren't pressurized in 1938, so she borrowed a system invented by Dr. Randy Lovelace, her good friend, a personal oxygen system that would let her breathe safely at altitude. So she takes off and gets up to altitude and finds she's flying through a storm, but she can't afford to go around it, so she flies through it. As she goes through the storm, she finds that her right wing tank isn't draining, and it's weighing her down, and switching between wing and belly tanks isn't helping. So she starts flying in a zigzag pattern. She flies with her right wing raised forcibly during that tank, then levels out to get back on her flight path. It was a sometimes harrowing flight, but she made it. She won the Bendix, and here she is shaking hands with Vincent Bendix after landing in Cleveland. Also after landing, she got right back in the plane and flew to New York City to add a women's cross-country speed record to the day's achievements. The trophy itself shows two figures, a globe, and a plane. It's made of brass and painted gold, which is why now it's all tarnished and green. Here's what it used to look like. Jackie entered the Bendix again in 1946 and carried this signed stamp cover with her, which I now own. Up next is the Harman Trophy, named for and established by balloonist and aviator Clifford B. Harman. It was awarded annually for most outstanding international achievements in the Arts or Science of Aeronautics. When the award was first given, there were four. Aviator, Aviatrix, Aeronaut, and a national award given to the outstanding flyer in each of the 21 member countries. The national award wasn't given after 1949, and in 1967, a new category for astronaut was created. Jackie won this one a lot. She won the national award in 1937, making it the first big trophy win of her career. She won the international Aviatrix award in 1938, 1939, 1940 to 1949, the war and post-war decade was taken as one. 1953, the year she broke the sound barrier, and 1954 and again in 1961. Here she is with President Truman after getting the 1953 award, and I love this picture of her kissing Floyd after that ceremony. Up front, that's Chuck Yeager, who had taught her how to fly a jet supersonically and also won the Aviator award himself that year. The Collier Trophy is an interesting one. The award was established by Robert J. Collier, publisher of Collier's Weekly Magazine, who was also a pioneer in air sports and president of the Aero Club of America. After debuting as a trophy on behalf of the Aero Club of America, it was then given annually by the U.S. National Aeronautics Association to the one who made, quote, the greatest achievement in aeronautics or astronautics in America, with respect to improving the performance, efficiency and safety of air or space vehicles, the value of which has been thoroughly demonstrated by actual use during the preceding year. The first recipient in 1911 was Glenn Curtis for his development of the Curtis Model E hydro airplane. So that gives you an idea of the kind of developments needed to earn this award. Jackie never won this one, but she was on the selection committee for the 1939 award. Remember that oxygen mask she used to fly above 16,000 feet on her Bendix winning flight? She campaigned hard to have the 1939 award go to its makers, Dr. Walter Boothby, Dr. Randy Lovelace, and Harry Armstrong. And she was successful. This is, of course, the event that solidified Jackie's friendship with Randy Lovelace, which becomes important on the issue of women in space when Randy led the medical testing of women. But I digress, and you can read it all right here. Clifford W. Henderson was, among other things, a driving force behind the development of the Los Angeles International Airport, as well as managing director of the National Air Races from 1928 to 1939. The trophy was originally presented to the outstanding pilot at the National Air Races, but the trophy was re-established in 1960 as one awarded to, quote, a living individual, a group of individuals, or an organization whose vision, leadership, or skill made a significant and lasting contribution to the promotion and advancement of aviation and aerospace in the United States. Jackie won this one in 1963. The year she established a Fédération Aeronautique Internationale World Speed Record and a Lockheed TF-104G Starfighter on a closed 100-kilometer circuit with an average speed of 1,203 miles per hour. These are just the three I was able to find on that trip. Jackie had a lot more hardware as evidenced in this picture of her Manhattan foyer sometime in the early to mid-1940s, judging by her age.  Her trophies came in all kinds, including this one from her husband, Floyd, a silver cup inscribed to supersonic Jackie from Floyd. So that's it. I just wanted to share some of my air and space trip with you guys and highlight some of Jackie's really interesting achievements and the neat pictures I've amassed over the years. Jackie's nearly full story is in Fighting for Space. There's a link in the description below. And, of course, I've got some more content about and inspired by her coming up down the line. Thanks for hanging out with me today. I want to say a special thank you to my Patreon and YouTube members for helping make the vintage space possible. If you want to join my support network and have access to my Discord, there are a couple of links to help you out below. And, of course, all my social links as well. See you guys next time.


My name is Evelyn Acham, I'm a climate justice activist from Uganda. I work with Rise Up movement as the national coordinator and secretary and I'm also an active member of Fridays for Future and a member of Global Choices as an Arctic Angel. Together with the Rise Up movement, I'm working on a campaign which involves educating school students about the climate crisis and we are also hoping that one day the government will add to the climate education to the school curriculum because it's very important to teach the next generation about the climate crisis because the next generation belongs to the young people. The climate crisis affects everyone but some people are being impacted more than others like people from black and brown communities, communities in the global south and women and children. So in Africa women are responsible for putting food or cooking food in their homes and providing all this food especially in rural areas and villages and in Uganda personally, personally I'm from Uganda and Uganda heavily depends on agriculture for, so many people depend on agriculture for survival and yet agriculture depends on the climate, it depends on the natural systems but because of the climate crisis, weather patterns are disrupted and we are seeing prolonged droughts, we are seeing a torrential rainfall, we are seeing devastating floods and these floods are destroying people's crops. The prolonged droughts are drying up water sources and food sources and this is forcing women especially in rural areas to end up going longer distances because the nearby water sources, the nearby food sources have dried up so they have to walk very long distances to look for this food, to look for the water, to look for these basic needs to feed their children, to feed their families and as a result they are exposed to trafficking, they are exposed to violence as they are resting in these temporary shelters and we also see that because of the limited resources like food and water, this leads to conflicts in these places and the women are affected during this conflict. There are so many ways women can be empowered and one of the ways is educating these women, taking young women to school and encouraging them to stay in school. We see so many projects that are being done by different women groups like we see the Malala Fund which is providing education to so many girls around the world and encouraging girls to stay in school. This is one of the ways we are able to empower girls like we see project drawdown stated that educating a girl is one of the ways to achieve climate justice.


Hi, this is Scott with the Lotech Institute with a quick video on how to change a bike tire so you don't get stranded. So I find the easiest way to work on a bike is to flip it over so you can take the tires off pretty easily. You'll want to move the gear down to its lowest gear so that the tire will come off a little easier. Undo the brakes, release the quick release by pulling the lever and spinning out and then you can work the tire and the wheel right out. On the front it's a little easier, just undo the brakes and release the quick release and the tire should come right out. Now to take the tread and tube off of the rim you're going to have to release whatever pressure's in there. With the Presta valve you have to push on this little valve after unscrewing it. If you have a shorter valve like a car tire you're going to have to find a pen cap or some other moderately sharp object to push inside the valve to release the pressure. Once all the air is out then with the valve stem towards the top work your way down around the rim leaving yourself some slack at the bottom where you can then work the tire and tread off. This takes a little forearm strength. If you want to use tools go ahead and get yourself some tire irons which are smooth and won't puncture your tube. And the way those work is you let the air out yet again and then opposite the valve stem you hook one of the tire irons underneath and hook it to one of the spokes and then use the other one as a lever to push and work your way around until the tire comes free of the rim.  Now you'll want to remove the old tube and look for a new tube that is the right size and it will be printed on the side of both the tube and the tire. I inflate it just partially just so it will have a little integrity to stand in there and I put the valve stem where the air pressure recording is on the inside of the tube or excuse me on the tire so that I don't have to search for it later when I'm pumping it up I can see exactly how many PSI it should have. Now the best way to put it on is the reverse of taking it off with your hands. You work your way down to the bottom keeping the tube carefully inside the tire not pinching it between the tire and the rim and you work it down using your forearm muscles to seat the tire fully in the rim. Now some people will use tire irons but it's very dangerous and you're very likely to puncture the tube and have to do the whole thing again so if you absolutely must be extremely careful not to trap the tube between your tire iron and the rim where you will puncture it and have to do this whole thing all over again so if you can do it with your hands that is absolutely the best way to do it but if you have new tires or some really tight rims sometimes you have to do this but again be very careful not to puncture the tube or you're in a world of upset. Then you pump up the tires to about a third of their pressure and make sure the tire is properly seated in the rim that is that it looks even all the way around you don't see any bulges or any tube poking out anywhere it's pretty rare that that happens but if it does you'll blow it up then pump it up to the full pressure. I've done the same thing on the other one as well once you're done inflating it you have to close the valve by turning on that presta valve if you have a presta. The reinstallation of the wheels is the same as before but just in reverse use the put the wheel in place tighten the quick release and then reattach the brakes don't forget to reattach the brakes in the back you just have to make sure to thread it properly through the chain and again reattach your brakes and that's it that's how you replace a tube thanks for watching I'm Scott with low tech institute check us out on facebook instagram and our website stay tuned for more videos on simple bike repairs coming up soon thanks a lot.


This is Mark Ringo, Business Account Manager at FileMaker, and I'm your host for today's Getting Rid of Paper-Based Process Web Seminar, where you'll learn how FileMaker's customers like Austin Convention Center and iScience have leveraged FileMaker Go to replace paper. But before we get started, I have some brief housekeeping notes on the next slide. For best experience, we strongly recommend that you participate in this Web Seminar with at least a broadband connection. If you have any problems or require online assistance at any time, please contact Citrix Technical Support at<PHONE_NUMBER>. Again, that number is<PHONE_NUMBER>. During today's presentation, you'll have an opportunity to type in questions. On the next slide, we will talk briefly about how to enter a question. Go to the Control Panel, click on Questions section to reveal the question section and enter your question and send. We'll cover as many questions as time allows at the end of our presentation. On the next slide, I want to introduce the FileMaker platform. The FileMaker platform is not just one product. It is a group of products and technologies that all work together. With the FileMaker platform, you can create custom business solutions on Windows and Mac with FileMaker Pro and FileMaker Pro Advanced. FileMaker Pro is our flagship product and it's what you use to build solutions. However, if you build solutions for a team of people, you'll want to use FileMaker Pro Advanced, which comes with power tools such as the Script Debugger, the Data Viewer, Database Design Report, and also allows for custom menus and much more. FileMaker Server is the hub of any successful FileMaker deployment, which allows you to host your FileMaker solution and provides automated backups and remote administration. And you'll need FileMaker Server to use our new FileMaker WebDirect, which is breakthrough web technology that runs custom business solutions directly in a web browser on a desktop or laptop with no web development skills required. FileMaker Go brings your FileMaker solution to your teams on iPads, iPhones, and iPod touch devices. All your FileMaker solutions created with FileMaker Pro will simply work on these mobile devices. And best of all, FileMaker Go 13 is free at the App Store. So anybody that's on the webinar tape, you've got an iPhone or iPad, go out to the App Store and you can download FileMaker Go version 13 for free and start playing with it. We've got a couple starter solutions that come along with FileMaker Go. On the next slide, I'd like to discuss the benefits of FileMaker Go. What if you can instantly update current inventory levels from the warehouse while scanning bar codes? What if you can capture digital signatures to close sales deals on the road? What if you can collect research data, including photos and audio files in the field? Also swipe through patient's medical records in the emergency room. And what if you could conduct teacher evaluations in the classroom? These are just some examples of FileMaker customers today who are leveraging iPads or iPhones for their business. On the next slide, I'd like to discuss why our customers have gotten rid of paper-based processes. Paper is hard to share with remote workers. The data on paper becomes very obsolete very quickly. And leveraging paper can be a very manual process. And the biggest issue that we see with paper is security. It's just simply not secure. And storage has become very, very costly. And then the biggest issue that both prospects and customers complain about is, with paper, you may have multiple versions of the truth. In fact, we've got customer-safe contractors and landscaping-type companies that literally now meet with their customers and they're able to provide them with a price quote right from their iPhone and iPad. And the customer can simply review. And if they accept the terms of the quote, they could use their finger and sign right there on the mobile device. They could also take a look at specific blueprints and make changes to the blueprints that the contractor provides them right from the mobile device. On the next slide, I want to discuss the Austin Convention Center business use case. Austin Convention Center transformed paper-based service order forms, work orders, and floor diagrams into a mobile application that provides a mobile workforce the ability to view, process, and reference event information across a facility that spans six city blocks. On the next slide, let's discuss how Austin Convention Center operated before FileMaker Go. The exhibitors' work orders were based solely on faxes and paper. The orders were keyed into a system, printed out, and placed into a binder with diagrams and other paperwork to start deployment or fulfill changes. This was a very manual process. On the next slide, let's look at how the Convention Center has become more efficient with FileMaker Go on iPad. The good news, Austin Convention Center was already using FileMaker Pro for their billing system so they could leverage the skill set that they already knew in FileMaker. They didn't have to learn anything new. They very quickly designed work order forms on the iPad. Employees now have real-time access to work orders, change orders, and floor diagrams and easy-to-touch interface. This led to fewer errors, faster installs, and increased customer satisfaction. But more importantly, they had a very compelling return on investment. With FileMaker Go for iPad, the project payback was less than four months with an annual ROI of 200%. In fact, according to the IT service manager, there was an estimated annual savings of 24,000. If you'd like to learn more about this business use case from Austin Convention Center or other FileMaker customers leveraging FileMaker Go on iOS devices, go out to FileMaker.com, learn solutions, then customers, and then stories. And you'll get an opportunity to browse through our library of customer success stories. And some of those, like Austin Convention Center, has a video that accompanies them. At this point, I'd like to introduce Jeremiah Hammond of DB Services. He's going to be taking us through the customer success story for iScience. Thank you, Mark. Today, we're going to look at a case study from iScience of a physical inventory count process that started out paper-based, transitioned to spreadsheets, and ultimately ended up as an iPad application in FileMaker Go. We'll focus on how easy it is to get up and running with an iPad application in Go, highlighting the ease of which you can set up a FileMaker solution to use the iPad's built-in camera to attach photos to a record, and then utilize barcode scanning for faster and more accurate data entry. So iScience's primary objective is to design what spaces and equipment are needed in new or revamped STEM facilities, and then procure that equipment for each space, so spaces meaning rooms, and then STEM facilities, so STEM stands for science, technology, engineering, mathematics, STEM facilities such as hospitals and laboratory centers, things like that. iScience has around 50 employees across the globe. They work on pretty big projects, facilities over one million square feet in size. One of their current projects, the University Medical Center for Louisiana State University, LSU, UMC, is this medical center is replacing Charity, the previous hospital that was rendered useless during Hurricane Katrina. There's a $1.75 million dollar budget for equipment and furniture, and construction was budgeted for about $1.3 billion to give you an idea of the size of projects iScience works on. In this particular case, this facility is expected to open July 1st, 2015. iScience itself is headquartered in Glendale, Arizona, but the majority of employees are on site at whatever project they're working on because these facilities are so large they have to manage everything on site. So iScience went through a couple of systems previously before the iPad application. So in the 90s, they used a paper-based system. You can actually see the paper form there on the left. These systems all center around counting physical inventory, and counting physical inventory only matters on projects, on facilities that are being revamped or being replaced. And the idea here is that these facilities want to reuse the equipment that was in the previous facility for the new one to save on how much it's going to cost to supply equipment into the new facility. So at the beginning of a project, iScience goes through and walks through the previous facility and catalogs all the equipment that's there. And the way it works is they send out teams of two, where one person has a clipboard with that paper form on it, and a second person has a film camera to take a photo of the equipment. So the first person, they'll walk up to a piece of equipment in a room, equipment like operating table or an MRI or a computer, what have you, they'll walk up to that piece of equipment and the person with the paper form starts filling in basic information about it, what's its serial number, what's its make, model, description, and then the location of that piece of equipment. So what building are they in in the facility, what's the floor, what's the room number, and then where exactly in that room is this piece of equipment located. And then the second person who's taking a photo will take the photo and then tell the person, hey, tell the person with the paper form, hey, this is photo number one of film roll three, so that the paper form could, you know, the person could fill in like okay that's that photo so they can come back to it and they can find it later if need be. So they can go, when they're looking at the inventory records they can go okay that inventory record I want to see that photo, okay that's photo one out of three. The, so back at the end of the day the teams would go back to the office and would transcribe what's on the paper form into a spreadsheet on a PC, so you'd have this master spreadsheet on a PC and then they would develop the film rolls and put the resulting photos in a photo album and then have a reference, they would put a reference number in each photo so you would go find it later. So needless to say the whole process was very time consuming. There was a mixture of electronic and physical data. You had double data entry with transcribing the paper form to a spreadsheet and then you had to haul around this physical photo album which, you know, it took a while to even find, when you're trying to find a photo it takes a while and sharing photos of course very inefficient. So there's plenty of places for improvement here. And so in the 2000s when laptops and digital cameras became more ubiquitous, I science transitioned from using the paper form to using a laptop and from using the film camera to using a digital camera. So the, the, there was no more double data entry needed because the person in the laptop could just enter in the data directly into the spreadsheet and you have a digital camera now so there's no physical, you don't need physical photos, you have all digital data. So that definitely saved a ton of time. But this process had its own inefficiencies. The photos were a big part of the inefficiencies. You had to transfer the photos from the digital camera back to a desktop, back to where the master spreadsheet's located. And when you transfer these photos you would have to worry about unique photo names. The, I science only had multiple teams going out, multiple teams of two each day. So when you have, when you take the, the digital cameras from all the teams and you move the photos to the computer, the desktop, you have to make sure you don't have any name conflicts. So you could either rename the photos and make sure all the photos have unique names so they don't override each other. Or you could make folders for each digital camera and each day so that you can just put their respective photos in those folders so there's no, no conflicts there. And then once you did all that, you had to update the master spreadsheet to reflect the changes, the new name or where the, you know, the folder structure. Either way, very cumbersome time consuming process. So the master spreadsheet itself would get very large and it would be hard to search because these spreadsheets would get to be over tens of thousands of records. Data entry is pretty inconsistent on the spreadsheets on the laptops because there weren't any drop-down lists, checkbox sets, ways to standardize input. And then they're also dealing with battery life issues on, on the camera and on the laptop. You, these, these laptops and cameras just wouldn't last throughout the entire day so they're scrambling for outlets and whatever room they're in and that definitely slows down the cataloging process. So these were the previous systems that were used prior to the iPhone application of FileMaker Go. So in, in 2012, High Science was beginning a project here in Indianapolis revamping the Wishard Hospital downtown and they, just by how the, the cards fell, they were supposed to have three years to do the project but they ended up only having one and because of the time crunch, they, they needed to find a faster way to do inventory besides using, they needed something faster than laptops and digital cameras. So they were thinking about having an iPad application. And so they started searching online for applications, for inventory applications, mobile applications and they just couldn't find anything that, that really fit their needs. They, you know, they found, they found systems that are either too complex, too bloated, didn't fit their workflow, were desktop applications, not mobile applications. They just, there wasn't really a good fit out there. And then, iScience ran into FileMaker, eventually ran into FileMaker and they, they took their, the inventory starter solution and realized, wow, this, this, this handles most of the, the, the problems we're trying to solve. So they started running, they customized Jerry, Jerry Club, the president of iScience, he, he took the starter solution from FileMaker and customized it to fit their workflow. And they ended up using that starter solution for the Wishard project, for cataloging inventory for the Wishard project. And I'll, I'll show you, I'll show you guys that here in a little bit. So the, the, the major problems that the iPad application was trying to solve, trying to, it, it needs to have the ability to use the iPad's built-in camera to snap a photo. It needs to store that photo in the inventory record itself so that you don't have to go hunting and finder for the photo if you want to look at it. It's just, when you see the inventory record, boom, there it is. So that increases just efficiency on that alone. And they wanted to use a barcode scanner to, to have information automatically populate into a new inventory record based on a tag number, based on that barcode. It's a tag number. And this, this actually what is relevant to the LSU project at the Wishard project is where they needed this barcode scanning to work. And I will, I'll, I'll show you guys that in a little bit. But that's where we, DB Services, came in. We, the, the starter solution handled the photo side and got that all working, but the out of population of data, we, we ended up doing for, for iScience. Okay, let's go ahead and dig in to these two systems. So I'm going to show, I'm going to go ahead and show the starter solution that iScience had for the Wishard project, the previous solution, and then I'll show you what their current system, the one that we built, how that looks. So, first thing we're going to do is to show the starter solution. I am going to go ahead and put that on my iPad. So to do that, I'm going to use iTunes. So let me get that going here on one second. My, my iTunes is trying to back up my iPad. See if I can get it going. Okay, good. All right, so in, on it, in iTunes, you would select your iPad here. So you got my iPad. And then you go to apps, and if you scroll down to the bottom, you should see FileMaker go in the list here in the apps list. And then on the right, you will see a list of documents for FileMaker Go. And all you do to get a FileMaker file on to go is you just drag from the desktop into this list of documents, the file that you want to open up and go. So there you go. Simple as that. Let's go ahead and get go up and running here. Let me show you guys that. Let's get that on the desktop. Okay. All right, so I got go here. Let's go to the device, let's open up the Wishard starter solution. Okay. So this is a list of, I got some sample data from the Wishard project, not a lot, just to handful of records here. This is a list view. So I'm just going to tap on one of them to take you to the detail screen. So this is really where Jerry customized, the iScience customized the system. So you'll see there's already some branding here. You got the iScience logo, you've got the name of the project. So Jerry, Jerry the president, he did all this. He customized the starter solution all in one weekend. I'll show you what he did, but it was enough for him to get up and running, and it solved majority of the requirements here. So he changed some of the styling here, changed a little bit of the way this looks. And then he removed fields from the screen here that weren't relevant. When you get a starter solution up and running, when you create a starter solution, there's already some fields there for you, some standard fields, there were just some that didn't apply to the workflow. So he removed some and then added ones that were relevant. So you've got this department, you've got room number, room name, you know, what's the item manufacturer, so on and so forth. So he went through, he made fields, he added them to the screen and he changed the labels here. And then he also put drop down lists where they made sense. You'll see the little arrows here.  So there's, you can standardize data entry. I can just click on that and if I go back up to the top, excuse me, you'll see there, put the value in the field. And so he went through all the fields where it made sense to standardize data entry and he went ahead and did that. And then he also added these checkbox sets here on the right, which are very similar, they're very similar to value lists, how to set them up. So he, you know, standardize data entry and he also made data entry faster in this case. You can just check, check, check, you just tap on it and there you go, tap on it. There you go. And then finally, the big thing, the big thing that this did is it had a photo field on it. The inventory start solution already had a photo field and it allowed, it allows you to use the iPads built in camera. So let me go and show you that. I'm going to make a new inventory record. I'm just going to name it test and you'll see here that you just tap on the field to take a photo. So I'm going to tap on that.  So just by that photo field alone, we solved the major problems with photos. No more need for a digital camera. You can use the iPads built in camera for this. And then a file maker automatically takes that photo and stores it with the inventory record that you're on. So there's no more hunting for photos and finders. And Jerry, iScience didn't have to do anything. It was just already there out of the box. So I'm going to go ahead and show you, even though it came out of the box, it's very simple to add a photo field. It's also very simple to add value lists. So I want to go ahead and show you how to do that. So I'm going to close this, then I'm going to, I'm going to go ahead and show you the desktop here. So to make changes to layouts, to make design changes, coding changes, you have to use FileMaker Pro on the desktop. FileMaker Go is meant only for, it's meant only for data entry. So I have the wizard solution up here. I'm going to go to that iPad details screen. And you'll see that's what we were looking at on the iPad. So let me go ahead and let me do the photo field first. So I'm going to go in the layout mode here. This is where I can make changes to the layout. Then I'm going to go up to the database, so File, Manage, Database. And then I want to make sure I'm in the inventory table, because that's where I want to add a second photo field to, so I am. So I'm going to type in photo to here to name the new field. And then I'm going to change the type on the right to container. Container fields are where you store binary data. So in this case, we're storing photos. Instead of we're not doing text, we're doing binary. So I've just made a container field, and I'm going to press Create. And there you go, the container field's been made. I'm going to go ahead and press OK here. And then I'm going to add the photo field to the layout. I'm going to use the field picker up here. And I'm going to scroll down to my new photo to field. At the bottom, then I'm going to drag it on the layout. I'm going to resize it so it fits in this little top left corner. And then I'm just going to save the layout up here. And that's it. That's all you need to do to add a new photo field to a layout. And I'll show you that this field works identical to this here in a second. So the second thing I want to show you is adding a new value list and how simple that is. So if you go to the dimensions field, I'm going to go here down at the bottom, use this. So let's bring in the inspector pallet. Go to the Data tab. And then right here, you've got edit box. That's what this field currently is set up as. It's set up as a free form field. Just type whatever you want. I want to change this to drop down list. And then values from where do you want to have your value list derived from. We're going to go ahead and make a new value list. So I'm going to press New here. Let's call it dimensions. Let's just add a couple test values, 5 by 5, 10 by 10, 15 by 15. Press OK. And then to be consistent with the way that iScience set up the field, I'm going to go ahead and add an arrow to show and hide the list. I'm going to check this little box right here. And I'll save my layout again. OK, so we've added the photo field. We've made the value list. So you can see the photo field is here. The value list, you've got the dimensions there. I'm going to show you that this works on an iPad. So I'm going to replace the old version with the new version. So to do that, I'm going to use iTunes again. And there's other ways to move files from the iPad or from a desktop to an iPad. iTunes is one as I'm showing. You can also attach it to an email and just send it via email. And then you can use Dropbox as well. So there's a number of ways you can do this, but we're going to use iTunes for this demo. I'm going to go ahead and drag it and override what's already there. You'll see it's asking, do you want to replace the old version? The new one I do replace. Let's go ahead and take a look at my iPad. I'll get that back up here. And I will show you that. Just open up Wishart again. Just go here. And you'll see that the Photo2 field is there now. This is the updated version. And that the dimensions does have a dropdown. So OK, so I'm going to move the current system that I signed using to my iPad here. So let me do that. And let's bring back up my iPad. OK, I'm going to open up the current system here. OK, the first thing you'll see that it looks pretty different from the starter solution. That's because we actually built this system from scratch. We didn't continue with the starter solution, mainly because the starter solution had other things that we didn't need in it. We just wanted to have a fresh start. And we decided to skin the application so the colors are more along the lines of the branding of iScience. iScience is blue, grays. So instead of the brown and the blues. And you'll see up here in the top that there's three modules. You've got the inventory module, which is the main module. And these other two modules are really set up. And they're for the auto population of data based on the tag numbers. So you've got financial asset module here. And you have a C equipment module here. And if you notice, you've got the asset number here. And this is what's on the barcodes so that this is what will fill in on the inventory record. And then the description from this asset number, make, model, serial number, et cetera, will fill in on the inventory number when you type in that asset number. And the C equipment is the same way. It just has a C number here. So these financial asset numbers and C equipment numbers are just numbers that are assigned from Louisiana State. They're from different databases. One's from financial database and other ones from a clinical engineering database. But the idea is iScience was leveraging this data to speed up data entry on the inventory collection side. So that's what they wanted us. That was the primary focus of this application was to build the ability to put in an asset number or a CE number and for all the information that it could to populate automatically so they can catalog numbers faster and more efficiently, which ultimately will save them money and it saves the client money as well, the hospital in this case. So I'm gonna go and show you how that works. I'm gonna make a new inventory record here. And so you'll see that the description's blank. We do have these filled in and I'll go over that in a minute. But the rest of it, like the details here, manufacturer make, model, serial number, et cetera, those are all blank. So all this information should fill in when I type an asset number. So I'm gonna do that manually. So I'm gonna go one, four, one, five, zero. So you'll notice that it didn't find anything here. We actually have an indicator that says if it found a match or not. So that this increases the accuracy of the input. So I noticed I mistyped, I added an extra one here. So let me get rid of one of those and I do that. There we go, now it says found and you'll see the description filled in and then the details here, the manufacturer make, model, serial number, et cetera, all filled in and that came from the financial asset number record that matched this asset number. So let me just show you that the CE number as well works. So once I clear up the asset number, notice all the information cleared itself out. So I'm gonna type a CE number in here. If we go, there we go. So the same information, description, manufacturer make, model, et cetera, all filled in. So it saved them a significant amount of data entry time and it made the data entry very accurate. So they wanted to go a step beyond this and they wanted to be able to, they wanted to be able to scan the barcodes and then have the barcode contents automatically populate the asset number or the CE number. So they used a third party Bluetooth scanner, handheld scanner for this, but you can also use FileMakers native barcode scanning and that's what I'm gonna show you guys here today. So let me go and I made a separate layout for the native barcode scanning. So I added a scan button here. Let me show you how that works. So let's make a new item and I'm gonna press the scan button and it's gonna bring up the camera because the camera is what's used to scan a barcode. So you'll see I have a barcode right here and I'll put it in front of the camera and it should capture it once it focuses itself well enough. There we go. And so you see it filled in the FileMaker, filled in the asset number from the barcode and it did the same thing as manually entering it and auto-populated all the data. So let me go and show you how easy it is to set up that scan button to set up scanning, barcode scanning with the native FileMaker capabilities here. So let's close this file and let's go back to the desktop because again we need to use FileMaker Pro in the desktop to do any design changes. So I'm gonna open up that same system and I'm gonna go and just use this, the main layout here to add the button. So I'm gonna go in the layout mode and then I'm gonna go to insert menu up here and go to button to add the button and the barcode scanning is just one script step which you can select from the standard set of script steps here. So I'm gonna do insert from device and then I'm gonna specify, I'm gonna pick the target field, I'm gonna pick the field that FileMaker is gonna put the barcode contents into. In this case it's gonna be the asset number field. So I'm gonna press okay there and then what are we inserting from? We're inserting from barcode.  Press okay and then we need to name the button, name it scan just like the other one. I'm gonna drag it here in the top left. That's where we got some room in the layout and then I'm gonna save the layout. So now we have our button here and now I'm gonna take this new version of the system and put it on my iPad just like the wizard changes we made. So let me get iTunes back out here. Let me drag this and press replace. And let's go ahead and open up my iPad again. Let's open up the inventory tracker system. So this is the new version. You'll see that I have the scan button here now in my iPad. So I'm going to make a new record and I'm just going to do the same thing as before. I'm gonna press the scan button and you will see that it works just like the other scan button does. There we go. So simple as that to add barcode scanning to FileMaker Go. Okay, so the final thing I want to show you here is I'm sure you're thinking how if you have a handful of teams going out with local copies of this application and gathering data every day, how do you get all that data back together? So there's a number of ways you can do this. In the case of iScience, they were totally fine with taking the copies the copies of the file from each iPad, all the copies from the iPad and importing them in manually into a master copy on a desktop. Let me go and show you how that works. Let me, I'm going to, I need to move a copy I'm going to move a local copy here onto the iPad and let me open that up on the iPad.  Okay, so I've got this, go to my device. All right, I've got this import file. This is a local copy. I just want to show you what's in it. So we have four records here and they just, each one have photos and this is just, these are all the inventory I took for one day. Let's just pretend this is all the inventory I took for one day. I got these four pieces of equipment that I did and I want to go ahead and get that into the master. So what I do is I close my copy here on the iPad and I go to iTunes and I do the opposite. Instead of moving something from the desktop into iTunes, I'm going to move something out of iTunes into the desktop. So let me drag, just click on this here, iTunes and I'm going to drag it to the desktop. There it is. And I'm going to open up the master. I have a master copy here on the desktop and I'll open that up, File Maker Pro. And you'll see there's five records in the master and once I'm done importing from the iPad copy, I should have nine. So if I go up to file here and go import records file, I'm going to go and select my, let's go select the local copy which I believe is right here. Okay, here's the iPad copy. So it brings up field mapping, a field mapping dialogue. So you need to make sure that everything's set up here appropriately. I'm just going from inventory. So the source here is the iPad copy. So I'm trying to import inventory records from the iPad to inventory into the inventory table in the master. So we're doing inventory to inventory and we want to arrange by matching names since these are identical copies of the same application. And I just want to make sure all the arrows are matching up here and they are. So I'm just going to press import and then just press that again and File Maker said, hey, we added four. Great, if I do a show all here, you'll see I have nine records now. And there are my records from the iPad. So that's what I signed for the other day and we could have gotten more elaborate on this method but for what they wanted for the LSU system, this the auto population and everything was so, you know, the increase in efficiency was so great that they didn't need the more elaborate syncing solution at that time. So the transition from the paper to the spreadsheet to the iPad application, it reduced time to take inventory threefold with much greater accuracy and it resulted in lower fees for iScience's clients, the hospitals and it also gave greater profit margins to iScience. So that's it. Thanks, Jeremiah. That was a great presentation and demonstration. Oh, well, hold on, Mark. Let me, I apologize. I do have one other thing here. Our services, if you're interested in DB services, helping you get up and running with a mobile application and File Maker Go, feel free to contact us. We offer support, development, training and coaching and licensing services. You can learn more at our website, www.dbservices.com. Thank you, Mark. On the next slide here, I wanna talk about some of the File Maker resources that we have available out on our website. These are important links that you can definitely copy down. As I mentioned at the beginning, File Maker Go 13 is free to free download. More customer success stories. I mentioned this at the beginning as well. We've got a whole library and videos of different success stories, like the couple that you heard about today. And then we've got traditionally every week, we've got web seminars on different topics, including this one, paper replacement. And then finally, we've got some training resources as well. So, next slide please. This being probably the most important File Maker training series, this is our basics. And this is actually a free download. So for the new folks on the phone today that are just learning about File Maker, this is a great training session for you to download, File Maker Basics. It's for beginning developers. And then if you get to the point where you wanna start developing solutions for your organization, we have the advanced version as well.


Hey guys Shea Bear 1000 here Today we're going to be checking out these three items that I got for free last week Let's see if any of them work Okay last week. I got some more free items. I get this fan. I got this Panasonic it's just a vacuum cleaner. It's got a dirt sensor in it These things are filthy But let's see if they work And we've got this this Bissell This carpet cleaner thing here We're going to see if they work this one actually has a heater in it now each one has its own little thing this one this fan Of course, it's missing the handle and it's missing this The knob on here and this I've done nothing to these except for this thing.  It does have a bag So I did take the bag out and emptied the bag It was full which can be a good sign Because apparently it was working when it got when the bag got full but this piece here Is broke now. I think I can fix that and this Is missing the handheld part for this for like doing your The clip in here is for like doing your couches or steps or whatnot It's no biggie if it works. Okay, if it works, you know, it should be worth 10 or 15 bucks to somebody so Let's get you set down here and we're gonna turn each one of them on I've got these two plugged in To a little extension cord over there This one I do not have plugged in yet Because it's got the ground and I'll have to take it over and plug it directly into the wall and Because it's got to be grounded because of it you you know It's around water and it also has a heater in it. So let's set you down here And let's see if they let's see if we can get them to work Okay, we're gonna start you off with the fan There's low now. Let's see if this thing works at least We know the fan works now what that dirt it's got a dirt sensor what that does is if it's green That means there's it's a clean area, which it is fairly clean since we're on the tile So area is not clean so you can keep going over until it turns green We're gonna plug this one in And we're gonna see if this behemoth works, and then we're gonna check each one. I'm out individually I've got a plug. That's uh I don't even have to turn this thing on So it does run it does has still have water in it. It's coming on So let's check this thing out and see what we got going on with it I can do this without making too much of a mess because we are in the kitchen Instead of the garage or outside that is because it is 11 o'clock. It's like eight minutes after 11 in the morning and 84 degrees with a real feel of 98 So we're staying in here where it's cool So let's uh, but it's got two brushes. So let's get you down here where you can see better Okay See if these beater bars are working the brushes Now we need to see if it'll spray water. I kind of like this whatever this does It kind of looks like it's got side pipes on it So it's supposed to dry the floor I think but let's see if it Most suck it up through here and if you turn this up here That's for your tools to work. Check this out Pull and lift here to a latch and this is where all your your dirty water goes So and we'll get you set up on another view Okay, what we got here on the bissel on the carpet cleaner Everything works except for it's not spraying water So we're going to do another video on how to fix that. I'm pretty sure I know what's wrong with it So let's move back over to this thing Now the fan I may end up keeping this myself if I do I'll put a handle on it And I'll go to a yard sale or uh Flea market I'll find an old radio or something or maybe a fan that doesn't work and get a knob That's no big deal. I think you need to buy them and what a lot of people didn't know about these things Is this hole right here? There's one in each side what those holes are for is uh Some of these you you could buy a stand form and that's where the stand would bolt in you can turn that fan either You know either direction so Let's see If this thing will pick up something So what I've done is I put a little bit of kitty litter there on the floor Let's see if this thing will pick that up. Okay. It seemed to pick up pretty good. Um, it's got An automatic floor leveler on it So I can't like put it down real close But uh, it did seem to pick it up pretty good May need some cleaning on the inside It kind of sounds like it's whistling it a little bit Usually that's telling you that your hose might have a clog or something in it like that So I cleaned up So everything works except for the Bissell does not spray So stay tuned for a video on that. We're going to get into that and I think we did. All right, so If I don't keep the fan that should be worth three or four bucks maybe five The vacuum cleaner It should be worth about five and if I can get that Bissell cleaner without the attachment I should be able to get 10 bucks out of it.  Thanks for watching and I stay tuned for how to fix the Bissell cleaner And uh, remember she bears the myth the man the legend. I'm gone for now. Bye. Bye guys. Take care


So we continue to serial jobs, which is basically making a file that defines what to run and then submitting it And you can leave and come back and watch it Then we talk about Monitoring the job processes progress and so on and this answers a lot of questions which people had yesterday Like how do I tell how much memory and time my job needs? What do I request and so on? Then array jobs, which is serial jobs multiplied by many things happening at once Then this is sort of a in a mission we talk about the module command This used to be on day one, but we wanted to spread out the non-example based stuff even more And then we talk about GPU computing and parallel computing So we're not talking here about how to write your own programs that do these But if you have a program that uses GPU or parallel stuff how to run it on the cluster And I think we probably will not get to this last part here. So we'll skip it and then that and Well, we'll talk about this at the end, but you can read these follow-up suggestions for where to Yeah, we're to go next So with that being said any other introductory comments Yeah, I'll quickly mention that basically today's work is like like yesterday we We got some interactive users of the cluster. We connected there. We we put some files there We run some jobs interactively and we got some interactive users done So today we are basically like trying to tell the machine to do our work for us And that is like we we just try to tell the cluster or the machine and the q-system and so forth and that okay We want something to be done and and then we Let let it do it and then we like reap the reap the benefits So everything is like built around that principle So you should think about it like bit of like a like a programming your workflow This is kind of the thing that we are going to be doing And this is done through these non-interactive jobs And all of this is like related that we are going to be having it's like everything is extended by from the non-interactive jobs forward So should we go forward to the first topic yeah, so let's see serial jobs Can close some extra things okay So how do you want to arrange this should see what do you want to talk and I'll type Sure, yeah, we have plenty of like small examples littered around this this full page so we can we can then like go through the The examples to get it. So what are serial jobs? So? Serial jobs like we previously run interactive jobs So basically just commands that were executed the compute nodes. So basically we had we had we told the queue system, okay, here's a command run it on the on the node in some cases we just wanted to have an interactive like command line in in a compute node, but okay This this works up to a point But this all everything here relies on human interaction with the system So basically you need to like be there and write the commands that you want to be executed And that scales only to the point of how many like command lines Do you want to keep open and like like we yesterday mentioned that like yeah if you had thousand laptops Could you like run thousand times your code on the thousand laptops like most likely not like you you would Spend your whole day writing commands on the different laptops and it would be like really an inefficient way of working I have a good analogy about this which I'll tell in the array job section Yeah, but but in the cluster system what you want to do is basically you want to codify Your your like what do you want the program to do now? What do you want to do you want to codify into these scripts and the scripts are basically like collection of commands That that you want to be executed and then you tell the queue to execute them And and you tell them give them to the queue and then the queue Once once the resources have been like you tell you tell it to get some resources Once the resources are resources are available the queue executes the commands for you and well So that is How it basically basically works So you want to like create like this kind of a file that Contains all the information of what you like basically instructions. So basically the The queue system is a really good like cook that can do whatever you want For for you do whatever you want as long as you give it a good recipe and this is kind of the idea Like you would need to specify that okay put the water make it boil Like put the pasta into the water and this this way like you need to give give it the instructions that it Requires and then it will produce you the the build that you wanted But if you leave out some of the instructions, it doesn't like try to fill out the blanks It doesn't understand what you're trying to do Unless you tell it like what what you're supposed to do And how this works is that uh Like we write these scripts. So if you reach out once scroll to the to the first uh script example so So here's like a simple First job script that you could write. So what do we have here? So basically the first line is usually the same like Usually people run their scripts with the bash interpreter. So bash basically means the shell like the command line basically That means the first line is is like always in place And with that you tell tell the system that okay run these commands Like in a command line So that that usually never changes The next few lines are if you remember remember from the interactive tutorial Interactive session that we had yesterday We gave these resource parameters to the q system like we gave in the command line with the s run We gave like give me some memory. Give me some time and uh We we specify these in in the command line, but uh well If you run want to submit the script instead you want to usually write the Requirements into the file itself. So basically these you write these commands like this This is like static form of these comments. So basically this hashtag and capital s batch And after that you can have some comments Or some some parameters for the q system and the q system parses basically through this file It goes through the file and then it like looks for these comments And when it sees these comments, it's like, okay I will add these requirements to the job requirements And when when it encounters first line that is not a comment It will like stop looking and and then it like assumes that okay all of the requirements are have been specified So the example here, uh, we just ask for five minutes of time We should start doing this. Yeah, you should probably write this. Yeah, so to organize. I'll make a directory Called kickstart By the way, did you get my screen share? Yes, okay, great uh, so So this will be my working space for now or should I put this in work directory? Uh, work target would probably be better, but it doesn't really matter about these small cases As a good, uh, rule of thumb is Better to go to the work directory and work from there there. Okay Okay, so Okay, so new directory. Oh, here I am Yeah, um So should I make this script? Yes, if you use this, uh, like this is, uh Easy editor called nano that you can use from the command line. There are other more powerful editors as well But they are more complicated to use and nano gives you lots of feedback. So it's easy to use so You can Cut this nano and let's say this yellow sh Okay And then basically copy paste the contents or write the contents there So the first line, uh, like I mentioned is the like, uh, interpreter like who who executes this stuff Uh, the second line we ask for time resources. So let we say that this job, uh Should take five minutes to run On the third line we ask for 100, uh Megabytes per cpu in this case It's a bit of a like, uh, we'll talk about this memory memory per cpu. You can use mem Just mem or mem per cpu. We'll talk about the difference later on But basically 100 megabytes of, uh, memory And then we set up an output file for the for the script. So in this case, um Yeah, hello out. So this is where the output will Turn out to be so the output way in this case We'll talk about a bit more in the monitoring But the output means like what the what it produces into the command Command output. Basically. Yeah So so what you would see if you would run this command yourself What kind of grain statements it would produce those will be redirected into the output file So in this case, we just run this one s run command of echo. So basically just print print hello User name you are from host node name And Save and run Yes control x to exit And say modified. Yes Yes, and then hello dot sh If I list what's here, there's this. Yeah, okay So if we look a bit a bit below to the documentation we can see there that That you then if you want to run this command, uh, you in the queue You you need you need to use this s batch command. So this s batch command is is Is it basically means that run this as a batch job and batch job means that well do it non-interactively in the queue So basically when you run this with the s batch, the queue will take over and it will run it for you So you reach out should we go press. Yeah Enter Yes, now we can Use for example slurm queue Which will work at some other places, but let's use it anyway It should work. We we had now it works. Yeah, it should be in other places as well Yeah, so it already run. So it it doesn't show anything because it already run and it produced the hello out. So if we Look at me So I'll use a program called cat which basically takes the concept the contents of a file and prints it Which in this case is nicer than starting an editor, which I'll have to go and close So here we go It shows I ran something Yes, so the green statement in the code was like printed out Or in the in the script it was printed out and it was redirected to the output file and then we we got what we wanted Of course in this case like this is like a really simple example. We didn't do anything really but we basically Case we We could have had done anything we wanted in the code like in the in the middle part like if you Show the slurmscript again region we can We could have instead of like the s run echo here. We could have Done whatever we wanted here. We could have loaded some modules To load some software. We could have run some software commands And then they would be executed in the node that we we ended up on And we could have specified some other parameters for the job So basically the whole workflow of Of our analysis like these commands that you would normally write as this kind of like a series Okay, I'll first run this command. I'll then I'll run They can then I'll run this group. We all could have put them into this Well after we have specified the resource parameters And and this is the idea of the serial job So basically you write this one script that you submit and then you put it there and of course Like I say one script. It doesn't mean that you need to have one script for all of your jobs It means for this specific task that you're trying to accomplish So you can have multiple of these and the good thing also about these is that they document what you're trying to do So so you can like when you're running some analysis or something and you like If you ever use let's say a tupiter For coding you end up into this or matlab You you end up Well any any id really like you end up into this situation where often you you start different You run different like commands And then you run them in different orders And you no longer know like how did you end up into the end point where you got like like and These like when you have this learn script you basically have a set order of Executions a set order of commands that the program runs and And then you know that okay, this is What should well what the program should do It should be let people try this out on sure like So if we put into the chat a quick poll Yeah Are you doing it? Oh, yeah, I can write it um Try running that example that Richard just did Yeah, I'm hoping it's certain about the formatting. Maybe maybe somebody in the HackMD can set the formatting so that it's uh, it doesn't become so capitalized. Yeah We needed more blank lines there. Oh, yeah. Yeah, by the way, I really like whoever adds other characters to the bar graphs Yeah But like it it wasn't that hard right like this is It's very easy to create this a cigarette tops So basically the only idea that you need to have in your mind is that okay What steps I need to do when I run the run the run the program that I Uh need to be done and of course this can be complicated like if you need to If you have a very complicated program, you might have a lots of complicated steps But but usually it's very easy to like codify what you're trying to do Okay, let's let's look at quickly like most of the people have managed to Yeah Do it. Uh, yeah, I will quickly Richard if you want to point the page again So so quick Note about the warning that we have on the page there run is batch not bash. That is very common So bash even though the file is named as dot sh That doesn't mean that it's a bash like it's it's it's going to be executed by bash But the idea is not to run it immediately. The idea is to let the queue run it On the background on the compute node. So you need to use s batch to submit to the queue So that is very common that people Like because they sound the same It's batch and bash like should I try it and let's see what happens So this is what you should not do unless you're locally testing So let's see it says it's queued But notice here now it puts the output to the screen So what actually happened is on the login node it went and ran each line in the file And the first well if we look at the file We see this is s run Hello, so it did request an allocation on another node And then it Ran this before it's like it basically like uh like when you run bash If those user and host them Uh with the currently existing user and host name So login tree is the current like placed where you're running it So it filled those and then it just ran it on a compute node where it printed like they already filled like Screen so so it's a bit of a like a mess. So but usually Usually it's a good idea It just creeped add something like let's say host name at the start So you know where it run and you know that everything is running on the compute node and everything works great But basically so in our pronunciation of s batch and bash Mix just remember that if you're trying to run it through the queue you need to use the s batch. Yeah Okay, so what's next is there really much more for Yeah, yeah, we could we could talk about like quickly about the uh, the resource parameters So yesterday we already have uh had had a discussion about when we did the interactive jobs Like what happens to jobs if they are They run out of memory or if they run out of time. So they are killed. So there's a bit of a leeway to the To the job. So so usually there's like an hour worth of leeway in the time department. So or something like that So if the job runs a bit over time, it's not immediately killed when the time is hit And same with the memory like if if it goes a bit Above the memory limit. It's not automatically killed. It's only killed if some other job needs that memory or it stays Like it goes way above the memory limit and but uh, so There was lots of questions, uh, uh, like how do you specify? How do you figure out these limits in the monitoring section? We talk about a bit more how how you can figure this out But like like said yesterday, it's good idea to like compare them to your local computer So if at your computer it takes like hour to run a simulation And it uses like you have 16 gigabytes of memory You might put like, I don't know two hours and 16 gigabytes of memory as the limit And then you can after the fact you can look what the actual usage was Usually you run these like pilot jobs. So these kinds of like test jobs Uh, when you start a new new thing new analysis or something You usually run one or two of these test jobs and see how it behaves and then you adapt Your parameters after that. Yeah, it's get killed then just like increase the limits and put another one into the queue Yeah Yeah, so so one thing Yeah, so so if you submit jobs you might sometimes need to also cancel the jobs So We we'll talk about the monitoring probably in the in the next chapter In much more detail, but but the canceling job is is something that's also Important so each of the jobs gets like this job ID You can figure out the job ID with let's say Richard, could you submit some like sleet job or something? Yeah, okay in Mmm, like I create like a Yeah, like a like here Richard will create like this kind of a Sleep job say five minutes Yeah Yeah Yeah, okay, so it prints the name of the computer the time Sleeps for five minutes and then prints the date You can see here that Richard is not putting any s bus parameters. So it will use the defaults here Yeah, uh when when you submit this kind of a script So the defaults are like hour of runtime of 500 megabytes of memory. Yeah So the job is now there. Can you see if the produces any output? Okay. Um with ls ls So I do see a file here Yeah, and you can see that the file name is a bit strange So the file name if you haven't specified an output file name It's this slurm dash and the job ID of the job. Uh if you run slurm queue now What does it what does the Slum queue job And for people in other universities what you said this does exist. Yeah, this is fcci now supported Yeah, that's great Should be in a helsinki university because they have multiple clusters. You need to talk to the helsinki university people Uh, they They have a bit of a different situation but What we see here in the output is that we have this job running. You can see the starting time how long it has run that it's running Where is it running and and on the left side you can see the job ID Whenever you submit a job to do there's like a huge database on the background That keeps track of all of the jobs of different users And and and there's the queue system that queue system. They basically allocates Different resources for the jobs based on like this kind of a resource priorities and algorithm that it runs on the background so basically Your job is given a priority based on your past uses and and your like re like the resources requested by the job and And well these kind of small jobs are immediately basically in the queue like that They usually run very quickly in the queue and it's currently running on the background So if we want to cancel this richard, what would you do? So we first would find the job ID Which I can find from the slurm queue or also when I submitted it and then As cancel Yeah, and now if we look at the slurm queue Yeah, there It's not it's gone. If we're going to slurm history now So slurm history you can give it also like this kind of a time Time format like let's say one hour so that you don't get all of the previous jobs that richard has run That's probably quite a bit of them, but you can see the last few lines there Okay, this is really wide Yeah, but the last few lines you can see at the bottom. There's like this Job ID and you can see Maybe on the right not Not really, but on the right. There's this It says that it's cancelled status Yeah, so you can see some of the jobs Completed and some of them cancelled. So basically you're like when you're usually using these queue system and these Non-interactive jobs You're firing away jobs that you have like brief program like tasks You're firing them away into the queue and if some of them like fail for let's say they have Insufficient time automatically means you then add up those and put them back into the queue again And you basically like manage like these scripts usually this way And sometimes let's say you you submit the job that you know won't finish in time It's usually better to just cancel the job and put another one with the correct time requirements into the queue Yeah, that that's pretty much it for for the Serial jobs one thing that is like Under the hood there are these partitions So basically all of there's lots of different compute nodes usually in a cluster like we mentioned on the first day Cluster comp is compromised of multiple nodes and multiple different kinds of Computers and usually like for example here in alta. We have many many different Generations of computers that have been purchased like in different times and then we have also Different like we have specified some compute nodes to be in some partitions and some in the others In some sites like in alto you usually don't need to specify this partition like There's this Like the script slurms should automatically like put you into the correct partitions but just in case like in many other sites for example in csc or Well, some of the fcci sites most likely you need to specify these partitions so So you can find the information either with the Either with the Swarm command or with the s info command which is like this bit more like the swarm command is wrapper for all of these different commands But but if you need to specify this partition when you submit the job You can do it by specifying either like dash dash partition equals partition name or like simply DOS dash p and then the partition name so Richard do you want to submit the The for example the sleep job into the Debug partition or something like that So so For example in alto we have this debug partition for like really fast jobs that is meant meant for like debugging for really small jobs But usually you don't need to specify about it depends on the site Yeah And this is really something that we worked on a little well a few years ago trying to make the defaults as useful as possible The best way to teach something is to make it where you don't have to teach it Okay. Yeah, if you want to submit if you look at the queue now Does it say what partition it's in it? Yeah, it ends up there probably Yeah Because it's in multiple partitions most likely notes. So, uh, oh, yeah, I think Yeah, that's probably the reason so I guess for us it expands debug to include all possible partitions because Why not? Yeah but but yeah, so so In other sites you might get like the mileage may vary but just in case you will know that there's this So basically all of the nodes can be There there can be various of these partitions. Yeah Okay So we have a full reference here of Many useful commands Yes, there are very various of these commands and various of the features in these espach and also in the Yeah, well in in the Slurm commands themselves a few of the interesting features like we'll be talking about how to like get multiple cpus and Speak mpi tasks later on But there's also like ease of life or like usability features such as like you can You can specify the the slurm to send you a let's say email once the job is finished or something like that There's features such as that But like if you want to help like you should probably discuss with us before you use like You can test them out, but at least like once I think we got banned from the alter ideas when somebody made like a array job that made these mails Pop up quite a bit. Yeah, so so you should be careful not to spam too much With these commands But there's lots of like interesting features here that you can use in this So but Without further ado, we probably should go with the exercises so you can test out this Test out these and we'll check the hekemd for any interesting questions, but but basically here are few Things you could Try out so in the first exercise just create like an batch job that runs hostname It's good idea to write yourself So you really get like a grip of how do you write these scripts because like it's very easy to like Not follow the exact form of the commands for example like like Many cases like people come to garage and they ask like why why does my job work? Like why why is it killed like or something like that and then we notice that there's a small typo in the Parameters or something like that in the espach's parameters and that is very common and it's nothing like it's just like That happens to everybody, but it's it's easy. It's better to like try it out yourself to write these so that you get like Like you can see the form of the parameters yourself because when we see the script then after after It doesn't work. We quite quickly recognized. Okay. There's a there's like a typo there So It's good idea to test it out So which exercises should people work on then? Yeah, I How much time should we allocate? Maybe we should have something like Me 15 minutes maybe it could be like 15 minutes and then 10 minutes of break and we presume at The zero of the hour um Yeah, I mean maybe yeah, like what what did you go from here once you're familiar with the editor and these parameters then everything else is Simple incremental work from that. So yeah, it's worth it. This is like a bit more time now rather than struggle later This is really that like the meat of the Meat of the thing so basically Uh It's very important to like get get a grasp of this because like everything is built upon these non-interactive jobs Like more like like if you want to use more than What you can run like more than you can run in command lines You need to be able to do this and that's why it's good to like do these exercises and try this out So in the first exercise like I mentioned, it's simple like A simple sbat script second exercise Is you can test out what we just like the canceling Uh of the of the job and the third exercise try to see like Completely uh for yourself like how the non-interactive workflow works So basically to meet this job that constantly does something in the background and will produce your output and then get out of there Like get out of the cluster completely come back and see that it's still running. That is very important to like get this kind of a like Workflow where you go to a cluster just to submit your jobs and then do some other stuff So that uh, uh, you don't have to like think about it until it's finished Should we actually give 20 minutes for the exercises and make the break until I think maybe maybe we should have a 50 minutes and then go through the exercises Not me But then should we go through the exercises after the break? We shouldn't put people in a position where it's a question between break and doing the exercises. So that's true. So, so let's let's How about um, okay, we do five to five to two Sorry five to one and then uh, 10 minute break and then we go through the exercise Welcome back so Let's see how we're doing here Simo has gone and added a poll to the bottom Did he manage to run the exercises? um, please Well, I guess this is a multi answer um Yeah put put up like uh, we can then probably use the We Use it to to see if some of the exercises are bad or good or whatever like if we add this kind of a Multi user multi answer thing. So you don't have to go the exercises in the sequential orders. You can uh, you can do them in Um, yeah Okay, so, um We thought now we can do the exercises or at least the first few as a demo um, or do you think that there's enough here now that we should move on I think we could like at least go through the like the first uh first like we basically did the exercise to Like which was the canceling top canceling, but we could go through the exercise one and exercise three or maybe exercise Exercise one. Yeah, actually To see what Okay, let's take a look then. I'll get my screen arranged Okay, so exercise one What do I do? So i'm in my kickstart directory here Yeah, so let's create a new new Uh file for like cgl exercise one. Yeah. Thought sh So it says make a batch job that just runs hostname Yeah So that's the command to run and what's the other freight work Well, first we always have to start with the bean bash thing at the stop at the top. Does it have to be bash? Uh, well, it doesn't have to be but but that is the most common like You can also have other interpreters, but it's usually tricky and usually you want to do other stuff Like in your job, you want to do other commands such as like uh load modules or you want to Move to a folder or something like that and you usually want to do like command line stuff So bash is the best one to use usually And then usually like always like these are basically something you You uh, it's a good idea to like get accustomed to writing all the time So basically like just put something into time and memory because like you done what There was questions in the hack md that what happens if you forget these and of course like you get some some like Defaults defaults there, but it's it's basically like Like you just need like I I highly recommend getting like this kind of a habit of writing like these first lines all the time like How to pilot like when you need to create a new script you just write these automatically. Yeah So, okay, we need to change the job name. So should we look at the reference? How do we set the job name and so what does that actually mean? Yeah, I'll push control z to minimize nano Why does that not work? We can look at the reference in the in the documentation. Oh Oh, yeah, okay. I was gonna show opening a manual page Let's see. So I see job that can be left As a like an extra for the bash course But yeah, so so you can specify a job name. So this is like if you have a lot of different jobs It's usually a good idea to put a job name for your like otherwise It's automatically interpreted from the comments that you're running or the name of the script that you're running but it it might be helpful for you to like like figure out what is the what kind of uh Program you're running. So it's easier for you to pass the output of the slurm history and so forth Yeah, okay, and then we need to specify output file. So how do we do that? So I remember that's dash o from somewhere else Yeah, it's either dash or dash dash output So so you notice that many of these commands have like long form and short form in the documentation here We usually use long form because that reminds you what is what is the And the parameter it's it's like it says it says It does what it says on the team basically like like it it but but you can also use this short form things And here richard has specified this wildcard This really nice dash j. What does that mean? So this means it will use the job id there So that means if I run it multiple times the output won't be overwritten Yes, these kinds of wildcards. There's many of them in the in the manual espach model so you can use various different wildcards to like Make your output like auto generate a bit more fancy output names. Yeah Okay, so I will Exit and save with yes Okay, and let's submit it mmm Check the output Can you check the slurm queue? Is it currently? Okay, it looks like it read And we see already there that the output file like richard specified this percent j there It got the output file got this Uh job id there. Can you run a slurm history? Let's take a short history Yeah So there we see that on uh, I think it was csl 48 It ran ran this command and we saw we can see that it it ran. Yes Okay, so what does the output file say? Mmm. Yes, so it matches Yeah, so it it ran ran there there was Okay Good question in the in the hack and the about like why do we need to specify the s run within the Uh, there's spats script and the reason behind that is like we'll talk about it even more detail in the monitoring but but basically Your when you submit a spats job, you can see there that there's like this hierarchy of different Steps in the in the output in the history. So basically the first Line it shows you job ID the full job like the what the full job consists of and then you see like these Uh separate steps. So these bats extern and zero. So what these mean is that like these are The job is like run in multiple steps and unless the steps are named Then the steps are like clumped together into these batch steps So so basically you will just run them and you don't necessarily know what what they actually did but sometimes you want to know what is the output of the of all like you need to see Like specify Uh, how how different steps work. So so basically see how how different steps behaved.  So that is the command host name So basically like you can so for for example, if you had a massive job and there was part of it that Read in the data and part that did a computation Or part that process data part did a computation. You could Allocate the time between them and realize which one was actually the slow one or not Yeah, yeah that kind of stuff and and also like you can do various other monitoring tricks and also, uh, when you're running these massively parallel chops or big parallel chops using mpi You usually need to specify this s run so that the slur and the mpi can communicate to know where the chops will be running There was also a good question that that So can you specify other parameters such as the partition or something in the s batch? a thing and The short answer is yes, like you can you can specify whatever s batch parameters There like arguments. So for example these mail mail Like where do you want the mail to end up or partition or partition to use or whatever and uh All kinds of stuff you can specify in the In the s batch comments like this where lots of different parameters that you can specify there and they're basically like You can also override these from the command line. Uh, so Richard do you want to try out? So for example here, we have the output file specified, but let's say we like Okay, let's leave it like this is what you would comment that so we'd leave it as it is Yeah, yeah, you can comment these like if you don't want them to be you can add another comment So then but let's say if the Richard wants to like this Submit this job, but he wants the output file to be a different in this specific case He can from the command line your command line Like it goes I can fix that But basically, uh, you can from the command line when you're doing the s batch like call you can overwrite this So these are basically the same parameters and and like if the like if there's no parameters set The defaults of the system are used if if you have in the script file Some parameters those are used and if you run something from the command line that overrides those So basically you have this kind of hierarchy of different commands that you can do Okay, so should we run it? Yeah Okay Yes, well It's probably done if I list we see New output file. Yeah And the old so Yeah, so I think we can move on to the monitoring section now that we are Like, uh, yeah, so the other other stuff is basically the similar kind of thing Uh, so you you basically have the Yeah, you basically What is good to uh, like what is important for this, uh, serial job is to is notice that that all of the Uh stuff is like done on the background somewhere Like once you you basically fire and forget it you give the task to the q and the q do does it for you And you it does exactly what you say it to be like exactly the kind of stuff you needed to do Yeah, but let's look at the monitoring. I think okay


The north-east Greenland ice stream has been observed to have a high degree of horizontal anisotropy which can lead to faster ice flow in certain directions. This anisotropy is caused by the crystalline structure of the ice which changes over time due to its interaction with the environment. This change in crystalline structure leads to a decrease in the strength of the ice making it easier to flow in certain directions. This article was authored by Tamara and Nina Gerber, David A. Lyon, Nicholas Moser-Rathman, and others.