Progress:
Tasks Accomplished:
- We have inserted the OpenCV code from Mr. Lin’s app, into your XCode project. Although, we haven’t been able to make much progress since due to an error that comes up every time we’ve tried to build our app; finding a solution to fix this error has taken up most of our time.
Problems Solved:
- We were concerned with the particular code we would be inserting into our XCode project, since we could not start from scratch due to a time crunch. As of now we are using Mr. Lin’s code from the app he has created to at least reach a starting point to see how OpenCV will meet our needs.
Lessons Learned:
- Not only do we have to deal with familiarizing ourselves with XCode, but additionally we need to familiarize ourselves with the common problems that cause the building of the app to fail. We came across the one in the picture below quite frequently.
- Through our struggle with this error below, we are more familiar with the OpenCV library and how to use it and why it is so important to reference it correctly in our code.
New Idea Identified:
- We may need to use a different image processor aside from OpenCV. OpenCV is very complicated and may not be necessary if we can find a simpler one that will still be able to accomplish our task.
- We figured out that by downloading the older versions of OpenCV, we obtain the files we are missing and by dragging them into our code, we are able to reference them. However, this will not work for all because it is an inefficient way of working plus we then get errors saying we don’t have other files. So, we are still working on referencing the files.
Problem:
Difficulties Encountered:
- We continuously received the “Lexical or Preprocessor Issue” that halted the progress of our app. Everytime we tried alternatives, typically more errors came out. Some alternatives we tried were:
- Switching the “Always search user paths” setting under “Build Settings” to YES.
- Renaming the title of our ViewController.m to ViewController.mm
- Checking if our “User header paths” were pointing to the Framework.
Missing Information
- We are not necessarily missing information. Any “missing information,” is information we are learning along the way, like what certain issues that pop up on XCode mean (like the issue we’ve been having listed above).
Equipments Required
- We have not come across any obstacles that require equipment we do not already have; our project is computer based. Although, we have created a membership for the iOS Developer Center.
Materials Missed
- We were introduced to the iOS Developer Center, an online location where we can post questions we have pertaining to anything iOS related, as well as search through similar issues others have had to find solutions. This will help us when we come across issues that we ourselves do not have the answer for.
New Risks:
- If we cannot get OpenCV to comply with our XCode project we may need to find a different image processing software.
- If we do use an alternative image processing software/library, will we have to write code from scratch? Will a sample code be online anywhere for us to use/work off of?
Show Stopper Identified:
- Getting our app to decipher numbers instead of colors; many trains’ symbols share the same color but differ in meaning (ex. the 4 and 6 trains have the same color but bring riders to different locations). A question that comes along with this though is if OpenCV is capable of doing so.
Personal Problems
- Schedule Conflict: Leslie and I have one less day together than many other teams. Her OpenLab time on Wednesday is during 8th period while Kate’s is during 9th. Therefore, this provides us less time to collaborate, causing us to have to divide more of our tasks.
Plan:
Proposals/Steps to Attack the Problems
- We will continue working through the issue this week. An additional issue we might encounter that we've known about from the start, is OpenCV's ability to recognize what we want it to (symbols of subway signs). An alternative is through the use of marking the areas in which we want to identify with technology similar to what the drone navigation team plans to use.
Action Items for the Coming Week
- Our main goal of the week is to solve the “Lexical or Preprocessor Issue” that keeps appearing in our XCode project amongst inserting Mr. Lin’s code.
Experiments to Conduct
- If the OpenCV code pulls through, we will need to begin testing it’s ability with our pictures, ones we have taken of subway symbols.
Ideas to Try
- We are going to try downloading the older open cv for the files we are missing. If that doesn’t work, then we will have to think of a plan B. WE are giving ourselves the week but after that, we need to start thinking of something else because we don’t want to stay halted forever.
Vendors to Contact
- If we cannot fix the issue we have encountered (Lexical or Preprocessor Issue) and decide to not use a different image processor (library), then we may have to contact the OpenCV Company ourselves to see if they can help us fix the issue specific to our project. Or we might post our problem on popular coding blogs (stackoverflow, apple developer chats, etc.) and see if anyone else knows how to fix the problem
Updated Schedule
- Fix this error by the end of the week
- Once OpenCV is running, start figuring out how to have our app identify the objects we want it to identify.
- Make some trips to subway stations to take pictures and get an idea of what our app should do (how it should maneuver, what it should learn to recognize, etc.) As well as identify alternative manners if we come to the conclusion our plan may not be suitable.
