Where do cyclists need the most protection? The box. This thought process has brought us to 19.3, delivering a quantum leap forward for cyclist safety and intersection efficiency when complying with California MUTCD 2014 Revision 3. Join us as we introduce the many anticipated features of 19.3 and how you can use it to improve safety and maintain the efficiency of all road users.
Watch past Webinar Wednesdays and view more GRIDSMART videos by subscribing to our Youtube channel.
Brooke: (00:02) Hi good afternoon everyone. Thank you for joining us today for the introduction to 19.3. My name is Brad McGee and I am the Marketing and Communications Coordinator at GRIDSMART. I will be moderating today’s webinar, so if you have any questions please wait until the end of our presentation when we open up the floor for a Q & A. Today we have Jeff Price GRIDSMART Vice President of Technology who will be introducing the new and improved features of 19.3.
Brooke: (00:38) Jeff, we’ll go ahead and let you begin.
Jeff: (00:53) Hi everyone. As Brooke said this is Jeff Price. I’m the GRIDSMART VP of Technology, and I’m going to introduce just a few of the things in GRIDSMART 19.3 that was just released. Really appreciate you all taking the time to learn some more about GRIDSMART and what we’re doing. Again GRIDSMART 19.3, the release came out about a week ago. Hopefully, you’ve had the time to read the changelog. If you haven’t I highly encourage you to visit Support at GRIDSMART.com, and you know you can do this without a registered account. You can see the changelog, and you can go see the 19.3 changelog, and it is a long list of new features, improvements, and fixes so make sure you’ve read through that you understand what’s going on. One thing I want to mention: despite the long list that you’re seeing, there’s a much longer list behind the scenes as GRIDSMART takes a big step into its future, and what I’m talking about there is the continued performance and stability and security improvements behind the scenes so that we can continue to deliver great new functionality on the GS2 to hardware.
Jeff: (02:05) Now, despite the long list today, I’m primarily going to focus on the very first bullet on that changelog, and that’s what the bulk of this presentation will be about and what that is is the new feature for bicyclists discrimination in the box to enable green extension for bikes. This new feature is available with Performance Plus Module, and we’re pretty excited about it. We’ve been working on it for a little while, and we’re really glad to get it into your hands and hear what you have to say about it. So with that, I’m going to jump right into bikes in the box. So what GRIDSMART has done with bicyclists is a little different than what’s been in the market today. So as I mentioned this is part of the Performance Plus Module, and when we compare bikes in the box versus stoplight discrimination which is the standard in the market today, what GRIDSMART is achieving with bikes in the boxes improved safety and improved efficiency.
Jeff: (03:05) And I think that’s that’s kind of special to state again: It’s not just more efficient it’s also safer. So one of the things you’ll see me highlight as I go through this presentation is the concept of safety first, but the way the GRIDSMART has approached this problem allows us to achieve safety first and efficiency by default. So how you setup bikes in the box is really it couldn’t be simpler to set up or to understand: a three step process draw the box just like you’ve drawn any other zones, define THE outputs, and publish the changes. And let me walk you through what that looks like.
Jeff: (03:45) So I’m going to click into an intersection. I’m going to go to the configure screen. I’m going to switch the flattened view. I’m going to click the new icon in the top left corner next to vehicles zone. Particularly it says box. And when I click on the box, it’s going to tell me how to drive. It’s just the same old GRIDSMART. Draw the box. So you see me draw the box, close it off. That’s actually it.
Jeff: (04:15) The only thing that you have from a box are extension outputs. Now you can have extension outputs for bikes or vehicles in this scenario on programming outputs simply for bikes. So the note there is that in the box we discriminate a bicyclist from a different vehicle. I’m also walking through the published workflow here. One of the changes is a 19.3 is a slightly modified published workflow where you’re going to have to authenticate with a username and password. So we authenticate and publish those changes. And that is literally it to setting up the box for bicyclist discrimination.
Jeff: (04:54) So what I want to show you next is a little bit about how that works. So what we have here is an intersection. One of our many test intersections and we’ve got some vehicles zones and we have a box in the center.
Jeff: (05:13) So as you’ll see as the vehicles motorized vehicles pass through this box, there’s no activation program with bicyclist outputs only. There’s a bicyclist approaches as he enters the box, we trigger the box for bicyclists outputs. So again vehicles passing through the box aren’t triggered an activation because there are no vehicle outputs, but a bicyclist traveling through the box does trigger outputs.
Jeff: (05:40) Let’s get another one of our test intersections, and in this scenario, we’ve got vehicles traveling through the box waiting at the red in the top left. There’s an entire platoon of bicyclists, and you’ll see as they enter the box we start making calls for bicyclists. When this platoon of bicyclists has to traverse the box, we will drop those calls meaning there’s no more bicyclist in the box. And as vehicles pass through, again, no calls for vehicles. Now you could program it to have calls for vehicles if you’d like. We expect most of you will be using the bicyclist extensions only.
Jeff: (06:22) Continuing on. Another example of an operating intersection the bottom of this screen is very hard to see there’s two bicyclists waiting for the light to change green which it just did. As these two bicyclists enter the box we get some, we see the box activate when they leave the activation stops because there’s no more bicyclists in the box. One of the things I wanted to note I’m gonna roll back that video a little bit. This will become important later. Those two bicyclists left the stop on at the same time and what you can see is one is clearing the box now. One is not quite halfway through the box. This sort of highlights the fact that bicyclists travel at different speeds.
Jeff: (07:04) So those guys clear the box. And now we have a new green coming up on the top right of the screen. We have a couple of bicyclists leaving this zone appear entering the box, triggering, again, bike extensions from the box. And then lastly coming from the bottom, we have a bicyclist running the red light also triggering an extension in the box while he traverses it until he is out of the box. And in the last example, I want to show you of this operating. In this scene there’s a bicyclist very small hard to see where I’m moving the mouse is stopped in the box and approaching from the bottom right corner is another bicyclist traveling at fairly high speed. This is again an example of bicyclists traveling and traveling different speeds. And one thing I’ll come back to in a second may be a little hard to see but both of those bicyclists actually cleared the box on an all red. So they actually didn’t need any green time to clear the box.
Jeff: (08:06) So what’s going on behind the scenes. Just as a little clue to what we’re doing behind the scenes is GRIDSMART is a tracking system. We detect and track all the moving objects in the scene. What we’re doing with bicyclists and in some other vulnerable road users is every object we’re tracking, we’re actually as it approaches the junction box where conflicts can occur, we’re running a machine learning algorithm on that to classify what type of object that is.
Jeff: (08:34) So to give you an example, in this case, this is the video with the slow bicyclist waiting for the light to change, and as he starts to move – I may come back to that.
Jeff: (08:48) So this cyclist starts to move you see a yellow dot the yellow dot get the black dot, again another cyclist, yellow dot and a black dot. We’re looking at that and we’re saying – the yellow dots saying there is a possible bicyclist or vulnerable road user. And then the black dot says, we’ve decided after looking at this for several frames and making several decisions, that that is certainly a bicyclist or a vulnerable road user. To give you another example of how this operates. This is a little more involved activity.
Jeff: (09:20) We’re going to see if there’s a jogger enter the box, a pedestrian behind two bicyclists, and then a third bicyclist making a left turn. So again you can see how we’re identifying – and we’re just sort of annotating this video for display purposes – to show you how we can identify vulnerable road users like bicyclists, particularly bicyclists, from other motorized traffic.
Jeff: (09:45) Now why do we want to do this in the box? And there’s two reasons and I kind of hinted at them earlier. Safety first. Efficiency by default. So let’s talk a little bit about safety. What if stop line discrimination is not 100 percent accurate? Now I’m not commenting on the accuracy of it. I’m just asking the question what if stoplight discrimination is not 100 percent accurate. In that scenario a false bike call, or what we call a false positive machine learning, at the stop line means that you have to serve a long minimum green for something that didn’t need it which is a dramatic loss of efficiency, and you have no opportunity to recover because you can only see the stop line. So that’s the impact of a false bike call. On the other hand with stop line discrimination with a missed bike call, it’s dangerous because cyclists have been trained to expect a long minimum green that you’ve previously been serving them, and you also again have no opportunity to recover from that mistake as once they leave the stop line in the field of view, you don’t know what happens in the intersection.
Jeff: (10:55) Now on the other hand in the box, a false bike call has an impact on efficiency but it’s significantly less because we can create only a short extension. Since the impact on efficiency is is less dramatic, we can air on the side of safety so to dramatically reduce and ideally eliminate any missed bikes. So we can do this much more accurate capture and detection of bicyclists in the box and still be more efficient. So that’s the safety-first approach. Always air on the side of safety.
Jeff: (11:35) And what I mean by efficiency by default, when we’re considering bicyclists in the intersection, what we look at with the California MUTCD, for example, is clearance time or the clearance interval. That clearance interval is about the box. It’s the time that it takes a bicyclist to travel from the stop line to the farthest side of a conflicting lane. So stop line discrimination assumes all bicyclists travel the same speed. It’s kind of a slowest common denominator. So even if stop line discrimination is 100 percent accurate it still wastes green time because not all bicyclists, in fact, the majority of bicyclists, travel faster than that slowest common denominator.
Jeff: (12:26) So to highlight those points I want to use some illustrative examples. And the first thing I want to note is a formula. And this is from the California MUTCD. This is on the left is the clearance interval. So the minimum green plus yellow plus red clearance, that clearance interval for bicyclists by the California MUTCD is required to be greater than or equal to six seconds which is considered to be the bike startup loss – how long it takes the cyclist to get going. And it’s plus a distance divided by a speed, and that distance is the distance from the stop line to the far side of the last conflicting lane plus six feet for the length of a bicycle divided by some speed – 14.7 feet per second – which is considered to be an average speed that a bicyclist will achieve from a stop line through the intersection. So that’s the formula to compute the clearance interval according to the California MUTCD. So let’s take that formula and apply it to a couple of intersections and see what that means.
Jeff: (13:34) In this test intersection, you can see we have a bicyclist stopped past the stop line ready to cross the intersection. This is an eighty-six-foot traverse according to the MUTCD. That should take 12.3 seconds. When this light turns green and the cyclist starts across the intersection, he actually clears that intersection in 7.9 seconds. So 35 percent faster than the MUTCD. Let’s look at another location. So this is back to the slow and the fast bicyclist I talked about before. The MUTCD is 12.9 seconds. We have a slow bike. We have a fast bike that never slows down. The first guy is 8.8 seconds which is 32 percent faster than the MUTCD. And the second bike who timed his traverse was only 4.8 seconds. And the interesting thing in this scenario was they both exited and cleared the box on all red. This was from a long PED cycle, but it still highlights the fact that unless you can see the box you don’t know if you need to give bicyclists longer greens or not.
Jeff: (14:41) So one more highlight in this scenario. Again this is a 92-foot traverse from the bottom left to the top right. We have two bicyclists that are going to enter the box traveling at different speeds from the same starting location. That first bicyclist clears in 9.1 seconds, and the second actually clears in exactly 12.7 right at the median and the norm for the MUTCD.
Jeff: (15:09) So all those scenarios, that was really efficiency. So we’ve maintained safety, but I showed you the impact on efficiency.
Jeff: (15:18) I want to come back to this other video where there was a bicyclist turning left. So just below my label, this is a left turn of 93 feet requiring 12.7 seconds according to the MUTCD. This bicyclist is in between traffic and in cars. When the light turns green, there’s startup loss. He starts his motion executing a left turn so we follow him through the intersection. In this scenario that bicyclist took 16.2 seconds to make the clearance. So that’s 28 percent longer than the MUTCD, meaning that theoretically by those rules he wouldn’t be safe.
Jeff: (16:00) So right now the California MUTCD says that we only need 12.7 seconds, but we can remember a time not too many years ago when pedestrians used to walk faster as well. So in this scenario, we can actually serve a longer green time for people who need it and a shorter green time for people who don’t need it. So that’s how our bikes in the box or the box operates for GRIDSMART. Because of that technology, there’s a couple other benefits that come your way with that feature. If you have the Performance or Performance Plus Module, we now have bike specific counting, and that’s described in the FAQ and in the changelog. So even if you’re not using the box for bike extensions like you can for the Performance Plus Module, you’re going to get improved bike counting in the Performance Module because of this technology.
Jeff: (16:55) Additionally, we’re better at detecting. We’ve always detected and tracked bikes, but it’s been improved significantly and very low contrast scenarios, and that’s true whether or not you’re using Performance or Performance Plus Module. That’s a base detection feature. So we’ve also tried to anticipate frequently asked questions and there’s quite a few of those 12 or 13 or so that are on the Support side right now, and I encourage you to take a look at those. Just to highlight a couple of them: Do bikes in the box also active a vehicle extension outputs if you have them on? And the answer to that is yes, a bicyclist is considered to be a subset of vehicles. So if you set up bike and vehicle outputs in the box the bike will activate both of those outputs. What kind of bike reporting is available? I’ve covered that a moment ago about the improved length-based classification. There is a specific length of six feet for bicycles and vehicles begin at 11 feet. So you can do a length-based classification and do a specific bicycle count. And I should note the best for bicyclists exiting stop line zones.
Jeff: (18:06) How does GRIDSMART discriminate bicyclists? This is a machine learning approach. Technically it’s a deep convolutional neural network that’s based on image characteristics.
Jeff: (18:19) The question is how can the box be drawn to cover crosswalks? At present, no. This is specifically about bikes and vulnerable road users that might be in the box. This is not for pedestrian zones as of yet, so I encourage you – like I said – that’s just a few of the highlights of the FAQs, and I’m sure you guys might come up with some other questions, but on Support at GRIDSMART.com, we’ve already drafted a box FAQ and answer some of those questions.
Jeff: (18:50) You might ask about what we’re planning in the future with improvements to this technology. Well, you can probably start to imagine where we might go with this. Obviously improvements, new features, and new functionality all related to bikes and other vulnerable road users. That being said – and this is represented in the FAQ – GRIDSMART is committed to relentless improvement. We’re rolling this feature out. We think it’s very good. We think it’s the best in the industry. We don’t think it’s perfect. And we want to make it perfect. So, we’re going to rely on you. We’re looking for your feedback, your feedback for where and how you would like to see things work in the future, your feedback if you see something we don’t expect. We want you, we encourage you to use your Sales Manager, your Field Application Engineer, and also I will note that there is a feature request form at support.GRIDSMART.com where we take community input. So all of those avenues are open to you, and we strongly encourage you to provide feedback. This is a new way of doing this. We’re not trying to put any stringent requirements on how you implement it. So we’re really excited about hearing what you do and hearing your feedback with the way this behaves.
Jeff: (20:07) So that’s how bikes in the box work. It’s really not that hard to explain. Draw the zone, set up the outputs, whenever there’s a bike we turn on those outputs. What you want to do in the controller, again that’s up to you, and that’s up to your controller manufacturer. And that’s how bikes in the box work.
Jeff: (20:24) With that, I want to shift gears just a little bit to wrap up today, and the reason why I want to discuss this is I’m not going to get too deep into it. There’s gonna be a future webinar that goes a little bit deeper, but we’ve changed a little bit about how you configure a GS2 with 19.3 and specifically, I’m going to refer to this as device configuration. And one of the things you’ve probably encountered if you’ve set up many GRIDSMART Processors is that there’s kind of two parts, right? There’s the intersection and how you want to detect and track vehicles, where you want zones, and how it interfaces with the controller, what the outputs are, and then there’s also the device itself. And the device is about the network, the NTP, date, time et cetera. And we’re separating those two concerns. And we’re doing that with some benefits for you as our users and customers. So to sort of bring attention to it, if you’re using a 69 Processor or earlier, and you go to edit the site settings, you may be familiar with this panel that has several tabs on the left as the network tab on the right as the date/time tab and in the date/time tab, there were NTP settings.
Jeff: (21:42) Now when you upgrade to 19.3 and beyond, and you go to the GRIDSMART Client, that panel will look like this, and you will notice there is no network tab and the date/time does not have the NTP. server in it.
Jeff: (22:00) So how do you set that up? And that’s what this will show you. It’s a browser-based device configuration now. So you would navigate generally on your, you know, in your lab bench. You would use your laptop and you would navigate to the device. You can log in now to the device, and this scenario I’m going to log in as a published user with the default published password. When I sign in, I can actually see any configured cameras that might be attached, and I can look at some diagnostics. So noted I logged in with a publish password, publish credentials. There really there are no changes I can make here because this is an administrative function. So I can get quite a bit of advanced diagnostics, I can get logs et cetera, but I can’t really do anything. So let’s switch to an admin view. So I’ll log out with publish and I’m going to log in with the admin and the admin credentials and default admin password. Please change the default admin password.
Jeff: (22:59) So now we get to see the cameras and then quite a few more menu options on the left. And in particular, you know their modules we can choose a new license. We can upload a license file or sync one from the cloud. We can add users, change passwords – again you should always change the default admin password. The location settings are here, and I’ll return to what that means in a minute. The date time et cetera. And in terms of the network, this is where the network settings are, and that first tab that says network, traditionally, these ship with DHCP, but if you want to use a static IP, this is where you would set that up. And this is where you would put in the NTP server. So this is the same basically that was in the GRIDSMART Client before.
Jeff: (23:47) Now I wanted to return to this concept about location. So you can actually do this on your bench in the lab back in the shop. You can program in the location. You can set up all the network information NTP server, static IP addresses, and all of those things without ever connecting a camera. So if you put in it aisle module. You know you’re going to take it to a TS2 cabinet, you put in a TS2 module, and you can do this all in the lab. You can set up the location, the network, the date/time, all before taking it to the field. So this is something, you know, our customers have been asking for for a long time. You know, can we do the basic setup without having a camera? And the answer to that is yes. Now you can, and you can actually do it without even having the GRIDSMART Client.
Jeff: (24:38) And the next thing I want to note with this device-based configuration which won’t have an impact right now with 19.3, but it will with our next release, is that the system operations panel has a way to push an update to this processor. So you have a connection to the processor. You can select an update file, and if you’ve downloaded an update stick from us before and there is an update folder that has a .binary file, a BIN file, you can send that update file. You’ll get a warning letting you know you’re about to update a processor remotely, and then you can continue on, and you can update that processor from your office without creating a USB stick.
Jeff: (25:27) So that, of course, you can’t update a 69 processor that way because this isn’t running on it yet, but the next release past 19.3, you will have that capability. So that’s a little bit of an intro for the device-based configuration. And again there’s gonna be a subsequent webinar later this month I believe where our software engineering leadership is going to dig into to everything in there because a lot of what’s going on is about networking and IT in order to bring us up to speed with enterprise security standards. And that really concludes what I wanted to say about 19.3 today, and I appreciate everyone taking the time to listen to me. And with that, I think we could take some questions if there are any.
Brooke: (26:20) Thank you so much, Jeff, and thank you, everyone, for attending today. As Jeff said, we’re opening the floor up for questions. This time, we’ll be doing it a little bit differently. So if you could submit your written question in the Zoom Webinar Chat, that will allow us to see those questions better, and we’ll do our best to answer them for you. We also just sent a message out so you should get a notification of where to type in your questions. It looks like we just got a question into Jeff. I’ll let you take charge.
Jeff: (26:55) So the question that we got. We got two questions that came in. We’ll start with the first one: The IP to get to the web UI is still the 1921680150.10?
Jeff: (27:06) Yes, that’s correct. If you’re connected to – that, by the way, is in the changelog, it’s one of the early bullets – if you’re connected directly to the processor with your laptop it is 1921680150.10. However, I will note that it is https. It’s a secure socket, not http, and it’s over a different port: 8900. But again that is documented as one of the early bullets in the changelog.
Jeff: (27:31) And then we have a second question: Why is it called 19.3 and not 7.0?
Jeff: (27:35) We’ve been putting this in the changelog for a little while with the note that this change was coming. The betas for this release started in March of 2019. This is hence the 19.3 release. The next version of the software we believe we will be running betas of in June that we expect, we’re expecting it to roll out after June. So what we’re seeing is these are going to be year-year-month releases, so year-year. month, and then if there are any patches above those, they’ll have a third number.
Jeff: (28:13) So the, uh, another question we had is: what about scooters?
Jeff: (28:22) So this release is focused on bicycles. We are, we have limited data on scooters where we believe we do a good job with that, but it’s, the product is about bicyclists other vulnerable road users are captured largely. We believe we will be calling that a feature in the future, but it remains to be developed to the fullest, but it works pretty well for most vulnerable road users. But this is about bicyclists.
Jeff: (28:57) Someone asked about a subscription service for this feature.
Jeff: (29:01) There is no, there’s no subscription service that GRIDSMART sells. This is just a Performance Plus Module which actually, the majority of our users have on their GS2s.
Jeff: (29:15) Another question: does it differentiate between bicycle and motorcycles?
Jeff: (29:20) Again this is one of the things that we predicted would be a frequently asked question and between bicyclists and motorcycles, it does a pretty good job, but it’s not perfect. So sometimes a motorcycle will be counted as a bicycle, sometimes a motorcycle will trigger an extension. The great thing is, is if it’s in the box, and it’s an extension, it’s traveling quite fast and gets through quickly and has a limited impact on on the operation of the intersection. And that’s being done by a combination of machine learning. So what it can see in the image and other characteristics of the tracking.
Jeff: (30:01) Let’s see. Let’s see, there’s a question also about the, how this webinar was specifically about bicyclists more information about security improvements?
Jeff: (30:11) There is an update coming to the user guide that’s gonna have a networking guide in the back and the webinar a little later this month is going to specifically address the security improvements.
Jeff: (30:22) Let me see. I’m trying to get these questions: Legacy Processors.
Jeff: (30:29) There are, I believe that you should have received emails from our CEO on this front. This process this update does not support the Legacy Processors. There will be no official software updates for Legacy Processors going forward.
Jeff: (30:47) Let’s see is it a requirement to set the network up before going to the field?
Jeff: (30:50) No. It’s not a requirement. It’s just an option.
Jeff: (30:54) And how accurate are the counts with bikes and clusters? Pretty good. If we get two bicyclists traveling close together, we’ve been offering to generate one count. So as I mentioned also, we’re counting based on bikes at exiting stop line zones. So we’re using the box to discriminate it as a bicyclist, but we’re counting based on what stop line zone, the exit, and where they went. We will be using these, uh, this feature to improve the counting significantly in the future so I believe we’ll do very well even with clustered bikes. Bikes with bike trailers will still be recognized as a vulnerable road user. And if it’s a bike, it will still be counted as six feet even with the tag along. We’re not discriminating those from other bikes at present.
Jeff: (31:47) There is a question about the Legacy Processor.
Jeff: (31:49) There is an upgrade program for Legacy Processors. I don’t have the details in front of me, but I know that’s been communicated to our distributors and to our sales team. So please reach out to your representative on that.
Jeff: (32:01) Let me see if I’m missing anything here. OK. Let me step over into these other ones.
Jeff: (32:10) Bike counts be added to existing reports. Someone asked what bike counts be added to existing reports or will they need to be separately reported?
Jeff: (32:17) So right now they’re actually integrated into the length based classification. And if you take a look at the FAQ on how we did that, a bicyclist will be six feet long and is the only object that will be six feet long. Everything that’s not a bicyclist will be, will start at 11 feet and that BIN is based on our length-based classification was always plus and minus three feet anyway. So an 11 foot is sort of the minimum vehicle size BIN that really is plus or minus three feet and a bicyclist is six feet. So the default BINs that are set up when you run a length based classification, that lowest length is only bicyclists now and it should be much more accurate than it was in the past.
Jeff: (32:59) Someone said do we assign box outputs to all phases in use?
Jeff: (33:05) That is entirely up to you. So you can assign as many outputs to the box as you would like. So if you want to trigger extensions on only two through movements then you would only need to put two – perhaps – two outputs. If you wanted to trigger extensions for all eight phases you could actually do that as well.
Jeff: (33:29) Someone, let’s see there’s another question. Where do we go here? Someone asked if the hardware for Legacy Processors will still be supported?
Jeff: (33:38) I’m not sure if they mean will the software? This software will not install on Legacy Processors and use this functionality beyond what those are capable of supporting. If you still have it running, you know, there’s a trade up program for GS2s that we’re supporting. All of the Legacy Processors there, I believe the last ones came out of warranty about three months ago. If you still have an operating intersection, and you’re still having, if you encounter some issues, we will, you know, we will look at that on a case-by-case basis in terms of software patches, but there will be no more official releases that will support Legacy Processors.
Jeff: (34:22) And the last question: someone was asking about pedestrian zones. The, uh, So we also had the Pedestrian Module, uh, that used to be a separate Pedestrian Module. We have pedestrian zones. That functionality is included in the Performance Plus Module, and the intent for the pedestrian zones was also safety and extensions. We know of some organizations that have maintained the faster walk speed for their walk signal, and then used extensions to extend the adjacent phase even when the walk signal stopped showing to account for slower moving pedestrians. That was the intent of our pedestrian zones. The technology that’s based on is not the same technology as this, but it will be in the future to improve those pedestrian zones.
Jeff: (35:19) All right. And I think someone was asking a question about the admin and the passwords.
Jeff: (35:29) The default passwords are going to be documented in your user guide. And again this doesn’t impact the Legacy Processor, the LPs at all. And the software won’t run on those. In terms of default passwords, consult the user guide and best security practices as obviously to have an administrator with an administrator password and to set up user accounts for that. It’s not we’re not forcing you to make any changes beyond what you’ve already been doing, but we can now support those things when they are required.
Jeff: (36:03) So I think there was a flurry of questions. So someone says can pedestrian zones be set up without marked crosswalks?
Jeff: (36:15) Yes. Yes, they probably could. What, I mean again here is GRIDSMART is very transparent. Pedestrian zones are based on, uh, they air on the side of safety as well. So with any type of moving objects in or near a pedestrian zone that’s not associated definitely with a vehicle, it’s likely to trigger a false activation. And that’s one of the things we’re talking about bringing this technology to bear on the pedestrian zones to improve their performance as well. But yes you can set up a pedestrian zone even without a marked crosswalk. So.
Jeff: (36:52) All right. Well, I think I think that that is everything I’m going to cover today. I really, again, want to thank everyone for participating. And Brooke I’ll let you close it out.
Brooke: (37:05) Thank you, Jeff. If your questions were not answered today, please feel free to reach out to us at email@example.com, and we’ll make sure we get a timely response to you. This webinar was also recorded so we will be uploading it to our YouTube account and we will send you a link to that recording once it’s live. So you can watch it if you didn’t get to see the beginning of the webinar, and so you can, of course, share it with all your colleagues. Thank you again, everyone.