Hello,

I am using a Kali-linux VM. I am currently trying to compile the project and follow the different steps of the README.md. On the Linux part

sudo sh ./src/scripts/linux/docker_compile.sh

I'm having this following error, what am I doing wrong ?

[100%] Linking CXX shared library libcppad_lib.so
CMake Error: failed to create symbolic link 'libcppad_lib.so': operation not permitted
CMake Error: cmake_symlink_library: System Error: Operation not permitted
make[8]: *** [cppad_lib/CMakeFiles/cppad_lib.dir/build.make:146: cppad_lib/libcppad_lib.so.1227] Error 1
make[8]: *** Deleting file 'cppad_lib/libcppad_lib.so.1227'
make[8]: Leaving directory '/src/build/lion/build/cppad/build'
make[7]: Leaving directory '/src/build/lion/build/cppad/build'
make[7]: *** [CMakeFiles/Makefile2:953: cppad_lib/CMakeFiles/cppad_lib.dir/all] Error 2
make[6]: Leaving directory '/src/build/lion/build/cppad/build'
make[6]: *** [Makefile:130: all] Error 2
make[5]: *** [CMakeFiles/cppad.dir/build.make:112: /src/build/lion/build/cppad/src/cppad-stamp/cppad-build] Error 2
make[5]: Leaving directory '/src/build/lion/build/thirdparty'
make[4]: *** [CMakeFiles/Makefile2:80: CMakeFiles/cppad.dir/all] Error 2
make[4]: Leaving directory '/src/build/lion/build/thirdparty'
make[3]: Leaving directory '/src/build/lion/build/thirdparty'
make[3]: *** [Makefile:84: all] Error 2
-- Configuration of fastest-lap

CMake Error at CMakeLists.txt:90 (install):
  install TARGETS given target "tinyxml2" which does not exist.


-- Configuring incomplete, errors occurred!
See also "/src/build/lion/build/CMakeFiles/CMakeOutput.log".
See also "/src/build/lion/build/CMakeFiles/CMakeError.log".
make[2]: *** [CMakeFiles/lion.dir/build.make:107: /src/build/lion/src/lion-stamp/lion-configure] Error 1
make[1]: *** [CMakeFiles/Makefile2:78: CMakeFiles/lion.dir/all] Error 2
make: *** [Makefile:84: all] Error 2
-- Configuration of fastest-lap

CMake Error at cmake/get-third-party.cmake:35 (find_package):
  Could not find a package configuration file provided by "GTest" with any of
  the following names:

    GTestConfig.cmake
    gtest-config.cmake

  Add the installation prefix of "GTest" to CMAKE_PREFIX_PATH or set
  "GTest_DIR" to a directory containing one of the above files.  If "GTest"
  provides a separate development package or SDK, be sure it has been
  installed.
Call Stack (most recent call first):
  CMakeLists.txt:18 (include)


-- Configuring incomplete, errors occurred!
See also "/src/build/CMakeFiles/CMakeOutput.log".
make: *** No targets specified and no makefile found.  Stop.

Thanks for you time

This PR adds six tracks. Track limits (left and right) have been constructed with Google Earth and exported to kml files (included). Both kml are post processed using fastest-lap Python command:

fastest_lap.circuit_preprocessor(options)

to produce a single .xml file included.

Tracks:

• Hungaroring
• Jarama
• Pau ville (city track)
• Vallelunga
• Varano
• Zolder

When a vehicle is loaded from XML, a nice feature to have would be that the program checks that all the inputs present in the XML file have been used, and to throw an exception instead.

Having this feature could help to identify typos in the parameters that might lead to catastrophic events. For example, if one writes <front-tyre/> instead of <front-tire/> , the whole data would just be ignored and the tire parameters wouldn't be loaded.

A way of doing this, would be that every time an XML element is read, make the software add an XML attribute _parameter_used="true". Then, after the car has been loaded, check that all the elements have this attribute set to true.

Provide a Dockerized build environment for Linux compilation. The dockerfile will pull ubuntu:latest, install the required build dependencies and drop the user into a bash shell. The compilation instructions can be followed from within the docker container.

I had difficulty building and running the library locally on my arch linux machine, either having difficulty compiling or having missing references to other packages. To avoid interference with any local machine configuration, this was the solution I came up with to build the project.

Changes

• Add: Dockerfile
• Add: Script to build the docker image and to run an interactive shell inside the docker container
• Update: lint README.md

Tested

I can run the example Python notebooks

Problems / Feedback

The package builds as the docker user and in the directory of the docker container. Some of the cmake steps generate files like examples/fastest_lap.py with absolute file paths referenced from the docker container, not the host machine. Files created within the docker container inherit root permissions.

The docker script will drop the user into a docker container and will not automatically build the project.

Hello, Thanks for sharing this great work and making it available on Windows!

I have an issue when trying to run the circuit_preprocessor in Python (Windows 10 - PyCharms). When I try to run your example script, I get the following error:

c_lib.circuit_preprocessor(c_options); OSError: [WinError -529697949] Windows Error 0xe06d7363

I am able to run optimal_laptime.py without any problem.

I was thinking it could be the paths could be the issue. What is the source of these relative paths I have to put in? If not, any ideas what it could be?

Thanks in advance!

Hi, I tried running cmake with the cmake .. command in the command line and it returned this. Any help with getting everything running correctly would be much appreciated!

-- The C compiler identification is AppleClang 12.0.0.12000032 -- The CXX compiler identification is AppleClang 12.0.0.12000032 -- Detecting C compiler ABI info -- Detecting C compiler ABI info - done -- Check for working C compiler: /Library/Developer/CommandLineTools/usr/bin/cc - skipped -- Detecting C compile features -- Detecting C compile features - done -- Detecting CXX compiler ABI info -- Detecting CXX compiler ABI info - done -- Check for working CXX compiler: /Library/Developer/CommandLineTools/usr/bin/c++ - skipped -- Detecting CXX compile features -- Detecting CXX compile features - done

Configure third party libraries 
=============================== 

-- Performing Test CMAKE_HAVE_LIBC_PTHREAD -- Performing Test CMAKE_HAVE_LIBC_PTHREAD - Success -- Found Threads: TRUE
-- Compilation of the required third party libraries -- The C compiler identification is AppleClang 12.0.0.12000032 -- The CXX compiler identification is AppleClang 12.0.0.12000032 -- Detecting C compiler ABI info -- Detecting C compiler ABI info - done -- Check for working C compiler: /Library/Developer/CommandLineTools/usr/bin/cc - skipped -- Detecting C compile features -- Detecting C compile features - done -- Detecting CXX compiler ABI info -- Detecting CXX compiler ABI info - done -- Check for working CXX compiler: /Library/Developer/CommandLineTools/usr/bin/c++ - skipped -- Detecting CXX compile features -- Detecting CXX compile features - done -- Configuring done -- Generating done -- Build files have been written to: /Users/saian/Desktop/fastest-lap-main/build/thirdparty [ 12%] Creating directories for 'lion' [ 25%] Performing download step (git clone) for 'lion' Cloning into 'source'... warning: unable to access '/Users/saian/.config/git/ignore': Permission denied warning: unable to access '/Users/saian/.config/git/attributes': Permission denied Already on 'main' Your branch is up to date with 'origin/main'. [ 37%] Performing update step for 'lion' warning: unable to access '/Users/saian/.config/git/attributes': Permission denied warning: unable to access '/Users/saian/.config/git/ignore': Permission denied [ 50%] No patch step for 'lion' [ 62%] Performing configure step for 'lion' -- The C compiler identification is AppleClang 12.0.0.12000032 -- The CXX compiler identification is AppleClang 12.0.0.12000032 -- The Fortran compiler identification is unknown -- Detecting C compiler ABI info -- Detecting C compiler ABI info - done -- Check for working C compiler: /Library/Developer/CommandLineTools/usr/bin/cc - skipped -- Detecting C compile features -- Detecting C compile features - done -- Detecting CXX compiler ABI info -- Detecting CXX compiler ABI info - done -- Check for working CXX compiler: /Library/Developer/CommandLineTools/usr/bin/c++ - skipped -- Detecting CXX compile features -- Detecting CXX compile features - done CMake Error at CMakeLists.txt:4 (project): No CMAKE_Fortran_COMPILER could be found.

Tell CMake where to find the compiler by setting either the environment variable "FC" or the CMake cache entry CMAKE_Fortran_COMPILER to the full path to the compiler, or to the compiler name if it is in the PATH.

-- Configuring incomplete, errors occurred! See also "/Users/saian/Desktop/fastest-lap-main/build/lion/build/CMakeFiles/CMakeOutput.log". See also "/Users/saian/Desktop/fastest-lap-main/build/lion/build/CMakeFiles/CMakeError.log". make[2]: *** [/Users/saian/Desktop/fastest-lap-main/build/lion/src/lion-stamp/lion-configure] Error 1 make[1]: *** [CMakeFiles/lion.dir/all] Error 2 make: *** [all] Error 2

-- Configuration of fastest-lap CMake Error at cmake/get-third-party.cmake:34 (find_package): Could not find a package configuration file provided by "lion" with any of the following names:

lionConfig.cmake
lion-config.cmake

Add the installation prefix of "lion" to CMAKE_PREFIX_PATH or set "lion_DIR" to a directory containing one of the above files. If "lion" provides a separate development package or SDK, be sure it has been installed. Call Stack (most recent call first): CMakeLists.txt:18 (include)

-- Configuring incomplete, errors occurred! See also "/Users/saian/Desktop/fastest-lap-main/build/CMakeFiles/CMakeOutput.log".

Hi Juan,

First of all I want to congratulate you on such a project, your fastest-lap looks really cool!

I've found it very interesting and I would like to deepen it. Because of this, I would like to build the project on my Windows machine, not just use the binaries you've provided.

I've seen that one of the third-party packages used by fastest-lap -lion- requires a Fortran compiler. Do you have any suggestions for any specific Fortran compiler on Windows as you have for Linux and Mac?

Thanks for you time!

Background

Build option CMAKE_BUILD_TYPE is 'mandatory' because STREQUAL expects an argument. Force the expression to evaluate early by checking the existence of CMAKE_BUILD_TYPE. This makes CMAKE_BUILD_TYPE an optional build argument. Defaults to Release. Fixes build errors when using Docker build script, where at this time, cmake build flags can not be passed into the script.

Tested

$ cmake --version
cmake version 3.23.2

Without changes

        Configure Fastest-lap                                                                                                                                
        =====================                                                                                                                                
                                                                                                                                                             
CMake Error at CMakeLists.txt:75 (if):                                                                                                                       
  if given arguments:                                                                                                                                        
                                                                                                                                                             
    "MSYS" "AND" "STREQUAL" "Debug"                                                                                                                          
                                                                                                                                                             
  Unknown arguments specified      

With changes prevents this error.

Checklist

Before submitting a pull request, make sure you satisfy all of the following points:

• [x] Give as much detail as possible on what is included within the pull request
• [x] Make sure that new additions are not already present in the project
• [ ] ~~If it contains source code, comply with the coding guidelines~~
• [ ] ~~Add new tests for new features~~
• [ ] Run and pass the tests using GitHub's workflows

Allowing the user to set a maximum energy limit for a lap (i.e. fuel limit per lap) could make this simulation tool very useful for racing series such as Indycar and Formula E.

Setting energy limits and power limits to each individual tire could also produce lap simulations that could tell us more about how drivers change their driving style in order to make the tires last.

Thank you for building this simulation tool!

-Hello! I have compiled with cmake the project, but at the time I try to run it, I get this message:

make[2]: *** No hay ninguna regla para construir el objetivo 'thirdparty/lib/liblapack.so', necesario para 'lib/libfastestlapc.so/. Alto. make[1]: *** [CMakeFiles/Makefile2:273: src/main/c/CMakeFiles/fastestlapc.dir/all] Error 2 make: *** [Makefile:141: all] Error 2

Any idea how to solve it?

Hi,

I'm trying to run the simulation multiple times and changing the vehicle model parameters between each iteration.

• I run the simulation on the car model.
• I modify the car model xml file with code
• I re-run the simulation...

The first iteration works but stops after with an generic Windows Error. Could it be that it doesn't like that I am loading a vehicle that is already loaded? Is there a way to unload_vehicle before load_vehicle again on the same xml? If not, do I have to rename the car model xml to something different every iteration.

Thanks

In most tracks, when a car takes a full lap, the total yaw angle steered is 360 (with the appropriate sign for clock/counter-clock wise tracks). But for example, in suzuka, which self-intersects itself, its zero. So automatize the computation of this number before the circuit preprocessor starts the computation, and feed it to the rotation constraint.

The C version of vehicle_get_property is

double vehicle_get_property(const char* vehicle_name, const double* q, const double* qa, const double* u, const double s, const char* property_name);

Provide a binding in python, with the form:

def vehicle_get_property(vehicle_name, inputs, property_name)

where inputs is a dictionary with all the required inputs (q, qa, u and s), which are written into their C version (const double*) inside the function. To do so, the program shall first inquire C++ the key_name, q_names, qa_names, and u_names (this needs to be implemented first)

The program should stop if a required variable is not present and if there's an unused variable inside the map.