Variorium Connector: kernel granularity and JSON by twilk10 · Pull Request #265 · kokkos/kokkos-tools

twilk10 · 2024-07-19T19:17:28Z

Updates to the current connector with updates such as json updates, energy estimation, device information. It has also been altered to get power information at the kernel level.

masterleinad · 2024-07-19T19:47:02Z

Please explain the behavior of the connector tool including options. What is the minimum variorum version required? We should check for that when trying to find Variorum via CMake.

masterleinad

Please provide sample output.

masterleinad · 2024-07-19T19:48:09Z

profiling/variorum-connector/variorum-connector.cpp

-#include <inttypes.h>
+#include <chrono>
 #include <cstdlib>
 #include <cstring>
-#include <vector>
-#include <unordered_set>
-#include <string>
-#include <regex>
+#include <ctime>
 #include <cxxabi.h>
 #include <dlfcn.h>
-#include <ctime>
-#include <chrono>
-#include <iostream>
 #include <fstream>
-
+#include <inttypes.h>
+#include <iostream>
+#include <regex>
+#include <stdio.h>
+#include <string>
+#include <unordered_set>
+#include <vector>


Which of these header files are actually required? Please make sure to only use what you need.

masterleinad · 2024-07-19T19:49:18Z

profiling/variorum-connector/variorum-connector.cpp

+int power = -1;
+int power1 = 0;
+int power2 = 0;
+int filemake = -1;
+long long time1 = 0;
+long long time2 = 0;
+uint32_t gdevID = -1;
+std::vector<float> gpu_powers;
+std::vector<float> gpu_powers2;
+std::string output = "";


What are all these global variables used for? Please add comments in the code explaining their usage.

masterleinad · 2024-07-19T19:51:16Z

profiling/variorum-connector/variorum-connector.cpp

 int type_of_profiling =
-    0;  // 0 is for both print power & json, 1 is for print power, 2 is for json
-bool usingMPI     = false;
-bool verbosePrint = false;
-bool mpiOutPut    = false;
+    0; // 0 is for both print power & json, 1 is for print power, 2 is for json
+bool usingMPI = false;
+bool verbosePrint = true;
+bool mpiOutPut = false;


Are all of these still used/necessary?

masterleinad · 2024-07-19T19:51:34Z

profiling/variorum-connector/variorum-connector.cpp

+/*void printFile() {
+
+    std::ofstream file("variorumoutput.txt", std::ios::app); // Open in append
+mode if (!file) { std::cerr << "Error creating the file!" << std::endl; } else {
+        std::cout << "File created or opened successfully." << std::endl;
+    }
+    file.close(); // Close the file
+i}*/


Please remove unused code.

masterleinad · 2024-07-19T19:52:12Z

profiling/variorum-connector/variorum-connector.cpp

+    file.close(); // Close the file
+i}*/
+void printFile() {
+  const std::string filename = "variorumoutput.txt";


Maybe make this configurable via an environment variable.

masterleinad · 2024-07-19T20:05:03Z

profiling/variorum-connector/variorum-connector.cpp

+        //          std::cout << "Number of Sockets: " << num_sockets <<
+        //          std::endl;


Suggested change

// std::cout << "Number of Sockets: " << num_sockets <<

// std::endl;

masterleinad · 2024-07-19T20:05:38Z

profiling/variorum-connector/variorum-connector.cpp

+    char *num_sockets_pos = strstr(s, "\"num_gpus_per_socket\":");
+    if (num_sockets_pos != nullptr) {
+      num_sockets_pos += strlen("\"num_gpus_per_socket\":");
+
+      char *num_sockets_end_pos = strchr(num_sockets_pos, ',');
+      if (num_sockets_end_pos == nullptr) {
+        num_sockets_end_pos = strchr(num_sockets_pos, '}');
+      }
+      if (num_sockets_end_pos != nullptr) {
+
+        std::string num_sockets_str(num_sockets_pos,
+                                    num_sockets_end_pos - num_sockets_pos);
+
+        num_sockets = std::stoll(num_sockets_str);


Please try using jansson here as well (and below).

masterleinad · 2024-07-19T20:06:25Z

profiling/variorum-connector/variorum-connector.cpp

+      std::cout << "  Gpu start power: " << gpu_powers2[gdevID]
+                << " Gpu end power: " << gpu_powers[gdevID]
+                << "   Energy Estimation:   "
+                << ((gpu_powers[gdevID] + gpu_powers2[0]) / 2) *
+                       ((temp - time1) * .001)
+                << std::endl;


Let's just not print anything to stdout but only to the file.

Sounds fine to me.

masterleinad · 2024-07-19T20:07:06Z

profiling/variorum-connector/variorum-connector.cpp

+  /*	std::cout << "kokkos library call\n" << std::endl;
+    if (usingMPI) {
+      variorum_call_mpi();
+    } else {
+     variorum_call();
+    }
+    time_t total_time;
+    time_t end_time;
+    time(&end_time);
+    std::cout << "End Time: " << end_time << "\nStart Time: " << start_time
+              << "\n";
+    total_time = end_time - start_time;
+
+    std::cout << "The kokkos library was alive for " << total_time << "
+    seconds."
+              << std::endl;*/


Suggested change

/* std::cout << "kokkos library call\n" << std::endl;

if (usingMPI) {

variorum_call_mpi();

} else {

variorum_call();

}

time_t total_time;

time_t end_time;

time(&end_time);

std::cout << "End Time: " << end_time << "\nStart Time: " << start_time

<< "\n";

total_time = end_time - start_time;

std::cout << "The kokkos library was alive for " << total_time << "

seconds."

<< std::endl;*/

@twilk10 Is this suggestion OK with you? If so, can you commit it?

It is good with me.

masterleinad · 2024-07-19T20:10:35Z

profiling/variorum-connector/variorum-connector.cpp

+std::ostream &operator<<(
+    std::ostream &os,
+    const Kokkos::Tools::Experimental::ExecutionSpaceIdentifier &identifier) {
+
+  os << "  Type: " << identifier.type << "";
+  os << "  Device ID: " << identifier.device_id << "";
+  gdevID = identifier.device_id;
+  os << "  Instance ID: " << identifier.instance_id;
+  //   output += " Device ID: " + std::to_string(identifier.device_id) +
+  //                      " Instance ID: " +
+  //                      std::to_string(identifier.instance_id);
+  writeToFile("variorumoutput.txt", output);
+  return os;
+}


Don't overload operator<< but just write to the output file directly.

masterleinad · 2024-07-19T20:12:28Z

Please use clang-format 8 for the indentation.

vlkale · 2024-07-19T20:21:16Z

Please explain the behavior of the connector tool including options. What is the minimum variorum version required? We should check for that when trying to find Variorum via CMake.

+1

@twilk10 Thanks for submitting this PR!

To provide an explanation of this connector tool’s options and a high-level behavior from the Kokkos user perspective: maybe you can add kokkosp_print_help() (like what is in space-time-stack).

twilk10 · 2024-07-19T22:38:41Z

Please explain the behavior of the connector tool including options. What is the minimum variorum version required? We should check for that when trying to find Variorum via CMake.

+1

@twilk10 Thanks for submitting this PR!

To provide an explanation of this connector tool’s options and a high-level behavior from the Kokkos user perspective: maybe you can add kokkosp_print_help() (like what is in space-time-stack).

Thank you I will work on getting that information up as soon as possible.

vlkale · 2024-07-20T02:23:16Z

Please explain the behavior of the connector tool including options. What is the minimum variorum version required? We should check for that when trying to find Variorum via CMake.

+1
@twilk10 Thanks for submitting this PR!
To provide an explanation of this connector tool’s options and a high-level behavior from the Kokkos user perspective: maybe you can add kokkosp_print_help() (like what is in space-time-stack).

Thank you I will work on getting that information up as soon as possible.

Thanks! Be sure to run clang-format-8 on each code file that you changed in this PR, as @masterleinad mentions in one of his comments. This is a prereq for your PR to be merged. Note that this is the CI check that doesn't pass.

twilk10 · 2024-07-20T03:00:43Z

Please explain the behavior of the connector tool including options. What is the minimum variorum version required? We should check for that when trying to find Variorum via CMake.

+1
@twilk10 Thanks for submitting this PR!
To provide an explanation of this connector tool’s options and a high-level behavior from the Kokkos user perspective: maybe you can add kokkosp_print_help() (like what is in space-time-stack).

Thank you I will work on getting that information up as soon as possible.

Please explain the behavior of the connector tool including options. What is the minimum variorum version required? We should check for that when trying to find Variorum via CMake.

+1
@twilk10 Thanks for submitting this PR!
To provide an explanation of this connector tool’s options and a high-level behavior from the Kokkos user perspective: maybe you can add kokkosp_print_help() (like what is in space-time-stack).

Thank you I will work on getting that information up as soon as possible.

Thanks! Be sure to run clang-format-8 on each code file that you changed in this PR, as @masterleinad mentions in one of his comments. This is a prereq for your PR to be merged. Note that this is the CI check that doesn't pass.

I ran clang-format 8 on it I will have to evaluate what went wrong and try it again.

vlkale · 2024-07-23T14:27:32Z

Please explain the behavior of the connector tool including options. What is the minimum variorum version required? We should check for that when trying to find Variorum via CMake.

+1
@twilk10 Thanks for submitting this PR!
To provide an explanation of this connector tool’s options and a high-level behavior from the Kokkos user perspective: maybe you can add kokkosp_print_help() (like what is in space-time-stack).

Thank you I will work on getting that information up as soon as possible.

Please explain the behavior of the connector tool including options. What is the minimum variorum version required? We should check for that when trying to find Variorum via CMake.

+1
@twilk10 Thanks for submitting this PR!
To provide an explanation of this connector tool’s options and a high-level behavior from the Kokkos user perspective: maybe you can add kokkosp_print_help() (like what is in space-time-stack).

Thank you I will work on getting that information up as soon as possible.

Thanks! Be sure to run clang-format-8 on each code file that you changed in this PR, as @masterleinad mentions in one of his comments. This is a prereq for your PR to be merged. Note that this is the CI check that doesn't pass.

I ran clang-format 8 on it I will have to evaluate what went wrong and try it again.

@twilk10 OK. You want to do something like:

clang-format-8 -style=file --assume-filename=../../.clang-format ../../profiling/variorium-connector/kp_variorium_connector.cpp > ../../profiling/variorium-connector/kp_variorium_connector-temp.cpp

You can diff in between to see whether and/or how the file has indeed changed and then mv the temporary file to the original file.

If that doesn't work, can you send the error output with the flag -Werror ?

vlkale · 2024-07-23T14:33:07Z

@twilk10 Can you look at @masterleinad 's comments particularly on printing output and parsing json with jansson? I think they are good suggestions and maybe you can commit those before committing other changes with clang-format.

Also, make sure to note to not include any unneeded headers.

twilk10 · 2024-07-23T14:38:33Z

@twilk10 Can you look at @masterleinad 's comments particularly on printing output and parsing json with jansson? I think they are good suggestions and maybe you can commit those before committing other changes with clang-format.

Also, make sure to note to not include any unneeded headers.

I will take a look and try updating withthe help of these suggestions.

twilk10 · 2024-07-23T14:45:28Z

Please explain the behavior of the connector tool including options. What is the minimum variorum version required? We should check for that when trying to find Variorum via CMake.

+1
@twilk10 Thanks for submitting this PR!
To provide an explanation of this connector tool’s options and a high-level behavior from the Kokkos user perspective: maybe you can add kokkosp_print_help() (like what is in space-time-stack).

Thank you I will work on getting that information up as soon as possible.

Please explain the behavior of the connector tool including options. What is the minimum variorum version required? We should check for that when trying to find Variorum via CMake.

+1
@twilk10 Thanks for submitting this PR!
To provide an explanation of this connector tool’s options and a high-level behavior from the Kokkos user perspective: maybe you can add kokkosp_print_help() (like what is in space-time-stack).

Thank you I will work on getting that information up as soon as possible.

Thanks! Be sure to run clang-format-8 on each code file that you changed in this PR, as @masterleinad mentions in one of his comments. This is a prereq for your PR to be merged. Note that this is the CI check that doesn't pass.

I ran clang-format 8 on it I will have to evaluate what went wrong and try it again.

@twilk10 OK. You want to do something like:

clang-format-8 -style=file --assume-filename=../../.clang-format ../../profiling/variorium-connector/kp_variorium_connector.cpp > ../../profiling/variorium-connector/kp_variorium_connector-temp.cpp

You can diff in between to see whether and/or how the file has indeed changed and then mv the temporary file to the original file.

If that doesn't work, can you send the error output with the flag -Werror ?

I am having trouble getting access to clang-format-8 but I can get other versions.

twilk10 · 2024-07-23T16:44:13Z

Please explain the behavior of the connector tool including options. What is the minimum variorum version required? We should check for that when trying to find Variorum via CMake.

+1
@twilk10 Thanks for submitting this PR!
To provide an explanation of this connector tool’s options and a high-level behavior from the Kokkos user perspective: maybe you can add kokkosp_print_help() (like what is in space-time-stack).

Thank you I will work on getting that information up as soon as possible.

Please explain the behavior of the connector tool including options. What is the minimum variorum version required? We should check for that when trying to find Variorum via CMake.

+1
@twilk10 Thanks for submitting this PR!
To provide an explanation of this connector tool’s options and a high-level behavior from the Kokkos user perspective: maybe you can add kokkosp_print_help() (like what is in space-time-stack).

Thank you I will work on getting that information up as soon as possible.

Thanks! Be sure to run clang-format-8 on each code file that you changed in this PR, as @masterleinad mentions in one of his comments. This is a prereq for your PR to be merged. Note that this is the CI check that doesn't pass.

I ran clang-format 8 on it I will have to evaluate what went wrong and try it again.

@twilk10 OK. You want to do something like:
clang-format-8 -style=file --assume-filename=../../.clang-format ../../profiling/variorium-connector/kp_variorium_connector.cpp > ../../profiling/variorium-connector/kp_variorium_connector-temp.cpp
You can diff in between to see whether and/or how the file has indeed changed and then mv the temporary file to the original file.
If that doesn't work, can you send the error output with the flag -Werror ?

I am having trouble getting access to clang-format-8 but I can get other versions.

I have solved this issue.

vlkale · 2024-07-23T19:02:21Z

Great! All checks have passed for clang-format-8. Can you address the comments by @masterleinad ? (You can commit suggestions if you agree).

I also updated the title to capture the changes you made in your code better.

@masterleinad Are there any other things to resolve here?

twilk10 · 2024-07-23T19:11:04Z

Great! All checks have passed for clang-format-8. Can you address the comments by @masterleinad ? (You can commit suggestions if you agree).

I also updated the title to capture the changes you made in your code better.

@masterleinad Are there any other things to resolve here?

I am currently working on updating the connector to address the comments made by @masterleinad

masterleinad · 2024-07-23T19:39:07Z

profiling/variorum-connector/variorum-connector.cpp

@@ -1,4 +1,5 @@
-//@HEADER
+//@HEADER140


Suggested change

//@HEADER140

//@HEADER

You still have HEADER140 here.

masterleinad · 2024-07-23T19:45:47Z

profiling/variorum-connector/variorum-connector.cpp

+std::ostream &operator<<(
+    std::ostream &os,
+    const Kokkos::Tools::Experimental::DeviceType &deviceType) {
+  switch (deviceType) {
+    case Kokkos::Tools::Experimental::DeviceType::Serial:
+      os << "CPU";
+      output += "Type: CPU";
+      break;
+    case Kokkos::Tools::Experimental::DeviceType::OpenMP:
+      os << "OpenMP";
+      output += "Type: OpenMP";
+      break;
+    case Kokkos::Tools::Experimental::DeviceType::Cuda:
+      os << "cuda";
+      output += "Type: CUDA";
+      break;
+    case Kokkos::Tools::Experimental::DeviceType::HIP:
+      os << "hip";
+      output += "Type: HIP";
+      break;
+    case Kokkos::Tools::Experimental::DeviceType::OpenMPTarget:
+      os << "openmptarget";
+      output += "Type: openmptarget";
+      break;
+    case Kokkos::Tools::Experimental::DeviceType::HPX:
+      os << "hpx";
+      output += "Type: hpx";
+      break;
+    case Kokkos::Tools::Experimental::DeviceType::Threads:
+      os << "threads";
+      output += "Type: threads";
+      break;
+    case Kokkos::Tools::Experimental::DeviceType::SYCL:
+      os << "sycl";
+      output += "Type: SYCL";
+      break;
+    case Kokkos::Tools::Experimental::DeviceType::OpenACC:
+      os << "openacc";
+      output += "Type: OPENACC";
+      break;
+
+    default:
+      os << "Unknown Device Type";
+      output += "Type: Uknown Device Type";
+      break;
  }
-  time_t total_time;
-  time_t end_time;
-  time(&end_time);
-  std::cout << "End Time: " << end_time << "\nStart Time: " << start_time
-            << "\n";
-  total_time = end_time - start_time;
-
-  std::cout << "The kokkos library was alive for " << total_time << " seconds."
-            << std::endl;
+  return os;


Define a function such as

kokkos-tools/profiling/space-time-stack/kp_space_time_stack.cpp

Lines 54 to 67 in 5e895a3

Space get_space(SpaceHandle const& handle) {

// check that name starts with "Cuda"

if (strncmp(handle.name, "Cuda", 4) == 0) return SPACE_CUDA;

// check that name starts with "SYCL"

if (strncmp(handle.name, "SYCL", 4) == 0) return SPACE_SYCL;

// check that name starts with "OpenMPTarget"

if (strncmp(handle.name, "OpenMPTarget", 12) == 0) return SPACE_OMPT;

// check that name starts with "HIP"

if (strncmp(handle.name, "HIP", 3) == 0) return SPACE_HIP;

if (strcmp(handle.name, "Host") == 0) return SPACE_HOST;

abort();

return SPACE_HOST;

}

instead. We don't want to make Kokkos::Tools::Experimental::DeviceType implicitly printable.

twilk10 · 2024-08-06T13:56:34Z

This is an update to the Kokkos-tool variorum connector and can be used to get the power data an
Tested on incremental HIP test on exascale machine using AMD style architecture.
The idea of change is to make this tool usable and change the functionality to retrieve power information at the kernel level as that is a more modern use for the tool.
This is a step in the direction of allowing users to measure their energy consumption while using Kokkos.
Features to be updated
-updated json parsing
-updated what is to be printed out
Features that were updated in variorum but others
-API to get power
Features implemented
-Equation to estimate energy usage until energy API is updated
-Moving the capture of data to the hooks so that the power data being retrieved is from inside the kernel
Outputs include device Id device type device kernel and power alongside power estimation
Also Outputs to a file that is made on the system. User can provide an environment variable to be used by uncommenting code but if not variorum will make a file for the user to put the information in.

Compatible with variorum version 6.0
Sample output;
name: Z4mainEUllRlE_ Device ID: 0 Instance ID: 1 DeviceType: SERIAL Energy Estimation 2679.104000

Rombur · 2024-08-06T14:01:57Z

You pushed your build directory. You need to remove it.

masterleinad · 2024-08-06T14:30:11Z

profiling/variorum-connector/kp_variorium_connector-temp.cpp

Remove this file.

masterleinad · 2024-08-06T14:30:36Z

profiling/variorum-connector/kp_variorum_connector-temp.cpp

Remove this file.

masterleinad · 2024-08-06T14:31:26Z

profiling/variorum-connector/varconnectsample

Remove this file.

masterleinad · 2024-08-06T14:32:07Z

profiling/variorum-connector/variorum-connector.cpp

@@ -1,4 +1,5 @@
-//@HEADER
+//@HEADER140


masterleinad · 2024-08-06T14:32:27Z

profiling/variorum-connector/variorum-connector.cpp

+//#include <cxxabi.h>
+//#include <dlfcn.h>


Suggested change

//#include <cxxabi.h>

//#include <dlfcn.h>

If you don't need it, remove it.

masterleinad · 2024-08-06T14:45:40Z

profiling/variorum-connector/variorum-connector.cpp

+    if (gdevID == 0) {
+      switch (gdevID) {
+        case 1: {
+          json_t* gpu_value = json_object_get(power_gpu_watts, "GPU_1");


Suggested change

json_t* gpu_value = json_object_get(power_gpu_watts, "GPU_1");

json_t* gpu_value = json_object_get(power_gpu_watts, "GPU_" + std::to_string(gdevID));

and remove all the switch cases.

masterleinad · 2024-08-06T14:47:13Z

profiling/variorum-connector/variorum-connector.cpp

+      output = "  Energy Estimation " + std::to_string(((power1 + power2) / 2) *
+                                                       ((temp - time1) * .001));


What's the unit?

masterleinad · 2024-08-06T14:47:24Z

profiling/variorum-connector/variorum-connector.cpp

    std::cout << "No MPI Option provided, not using per rank output"
              << std::endl;
-    usingMPI = false;
+    //  usingMPI = false;


Suggested change

// usingMPI = false;

masterleinad · 2024-08-06T14:49:05Z

profiling/variorum-connector/variorum-connector.cpp

+std::ostream& operator<<(
+    std::ostream& os,
+    const Kokkos::Tools::Experimental::ExecutionSpaceIdentifier& identifier) {
+  gdevID = identifier.device_id;
+
+  output +=
+      " Device ID: " + std::to_string(identifier.device_id) +
+      " Instance ID: " + std::to_string(identifier.instance_id) +
+      " DeviceType: " +
+      deviceTypeToString(static_cast<Kokkos::Tools::Experimental::DeviceType>(
+          identifier.device_id));
+
+  writeToFile(filename, output);
+  return os;
 }


Please don't introduce an overload for operator<< but use a stringstream or write to the file immediately instead.

masterleinad · 2024-08-06T14:50:17Z

profiling/variorum-connector/variorum-connector.cpp

+  writeToFile(filename, "name: " + std::string(name));
+  gdevID      = devID;
+  auto result = Kokkos::Tools::Experimental::identifier_from_devid(devID);
+  std::cout << result;


Please don't print to cout anywhere but only to the output file.

masterleinad · 2024-08-06T15:42:13Z

Sample output; name: Z4mainEUllRlE_ Device ID: 0 Instance ID: 1 DeviceType: SERIAL Energy Estimation 2679.104000

Please provide output from the incremental tests or so.

masterleinad · 2024-10-14T18:49:36Z

profiling/variorum-connector/variorum-connector.cpp

+// Initial and final power values for a kernel
+double global_power[2] = {0, 0};
+// Initial and final time value for a kernel
+long long global_time[2]    = {0, 0};
+uint32_t global_device_id   = -1;
+uint32_t global_instance_id = -1;


Obvisously, this tool is not thread-safe.

Fixed issues myself.

JBludau · 2024-11-15T14:27:12Z

profiling/variorum-connector/variorum-connector.cpp

+uint32_t global_instance_id = -1;
+std::string global_filename;
+std::string global_kernel_name;
+std::string global_device_type;


why do we need so many global variables?

We need to record a bunch of information in the "begin kernel" calls that we are using in the "end kernel" calls. We can't pass that through the API interfaces directly.

janciesko · 2025-01-15T18:20:57Z

Might be a good idea to move forward with this PR

masterleinad · 2025-01-15T18:42:17Z

Might be a good idea to move forward with this PR

A review would help. 🙂

dalg24

replying to #265 (comment)

I will defer to you.

dalg24 · 2025-01-15T20:21:44Z

profiling/variorum-connector/variorum-connector.cpp

-    variorum_call();
-  }
+  auto result = Kokkos::Tools::Experimental::identifier_from_devid(devID);
+  global_kernel_name = std::string(name);


Suggested change

global_kernel_name = std::string(name);

global_kernel_name = name;

Same comment everywhere

dalg24 · 2025-01-15T20:24:01Z

profiling/variorum-connector/variorum-connector.cpp

+  json_t* my_power_obj = nullptr;
  my_power_obj         = json_object();


Suggested change

json_t* my_power_obj = nullptr;

my_power_obj = json_object();

json_t* my_power_obj = json_object();

Fragment from previous version, remove my_power_obj. We're using root now instead.

dalg24 · 2025-01-15T20:25:30Z

profiling/variorum-connector/variorum-connector.cpp

+  if (!root) {
+    fprintf(stderr, "Error parsing JSON: %s\n", error.text);
+  }


Consistency: use std::cerr

janciesko · 2025-01-16T21:30:45Z

Thanks @masterleinad for adding the CI testing. Seems to compile fine with Variorum for me.

janciesko · 2025-01-16T21:31:01Z

I am ok with this if CI with Variorum succeeds.

dalg24 · 2025-01-17T11:57:54Z

.github/workflows/build-with-kokkos.yml

          cmake --install build-with-${{ matrix.preset }} --prefix=${Kokkos_ROOT}
      - name: Build Kokkos Tools, enabling examples
        run: |
+          export CMAKE_PREFIX_PATH=${CMAKE_PREFIX_PATH};${VARIORUM_ROOT}


I expect the environment variable already adds it to the search path

kokkos-tools/cmake/configure_variorum.cmake

Line 19 in dd08b98

find_package(Variorum QUIET)

Apparently it is spelled with an uppercase V.
Please adjust your env variable accordingly and remove the line I highlighted.

The previous commit had Variorum_ROOT as environemnt variable and didn't find variorum.

kokkos-tools/cmake/configure_variorum.cmake

Lines 8 to 10 in dd08b98

if(DEFINED ENV{VARIORUM_ROOT})

set(Variorum_ROOT $ENV{VARIORUM_ROOT})

set(MSG_NOTFOUND "check VARIORUM_ROOT environment variable ($ENV{VARIORUM_ROOT})")

shows that it should be all uppercase.

That configure cmake file logic is absurd and need fixing.
(On my cell can't navigate easily but in short it should not write to Variorum_ROOT that is nonsensical)

.github/workflows/build-with-kokkos.yml

Tyler Wilkerson (kuw) added 3 commits July 15, 2024 14:41

first commit number 3

2fb4b91

variorum updates

554b7f9

variorum updates

c4e7b0a

masterleinad reviewed Jul 19, 2024

View reviewed changes

clang update

4e88454

vlkale changed the title ~~Varconnect~~ Variorium Connector: kernel granularity and JSON Jul 23, 2024

masterleinad reviewed Jul 23, 2024

View reviewed changes

Tyler Wilkerson (kuw) and others added 2 commits August 5, 2024 15:37

updated based on concerns

1abd450

Merge branch 'kokkos:develop' into varconnect

0c5d95f

Tyler Wilkerson (kuw) added 2 commits August 6, 2024 10:15

remove build directory

e9971f8

varconnect deleted

69c8a4c

masterleinad requested changes Aug 6, 2024

View reviewed changes

remove unneeded files

6c8a4c7

tpatki mentioned this pull request Aug 6, 2024

Update Kokkos Variorum port to report energy. llnl/variorum#574

Open

masterleinad reviewed Oct 14, 2024

View reviewed changes

JBludau reviewed Nov 15, 2024

View reviewed changes

dalg24 reviewed Jan 15, 2025

View reviewed changes

masterleinad added 3 commits January 16, 2025 15:56

Replace fprintf

94c8817

Don;t call std:string constructor unnecessarily

083d345

Build variorum

45c1620

janciesko approved these changes Jan 16, 2025

View reviewed changes

masterleinad added 6 commits January 16, 2025 16:32

Simplify

75e4bfd

Fix formatting

281914c

Install and set Fortran compiler

b915c2f

Install Jansson

eff8334

Simplify installation

c765e50

Variorum_ROOT -> VARIORUM_ROOT

b117cf8

dalg24 reviewed Jan 17, 2025

View reviewed changes

masterleinad added 4 commits January 17, 2025 07:49

Don't set CMAKE_PREFIX_PATH

40dae3d

Fix typo

d0807bc

Skip Variorum test

5f80c3d

Don't use GTEST_FILTER

e8468da

dalg24 reviewed Jan 17, 2025

View reviewed changes

.github/workflows/build-with-kokkos.yml Show resolved Hide resolved

dalg24 reviewed Jan 17, 2025

View reviewed changes

.github/workflows/build-with-kokkos.yml Outdated Show resolved Hide resolved

Improve comment

37aab14

masterleinad reviewed Jan 17, 2025

View reviewed changes

.github/workflows/build-with-kokkos.yml Outdated Show resolved Hide resolved

Improve comment again

d0e4f6c

dalg24 approved these changes Jan 17, 2025

View reviewed changes

dalg24 merged commit 2f784b3 into kokkos:develop Jan 17, 2025

		// std::cout << "Number of Sockets: " << num_sockets <<
		// std::endl;

	Space get_space(SpaceHandle const& handle) {
	// check that name starts with "Cuda"
	if (strncmp(handle.name, "Cuda", 4) == 0) return SPACE_CUDA;
	// check that name starts with "SYCL"
	if (strncmp(handle.name, "SYCL", 4) == 0) return SPACE_SYCL;
	// check that name starts with "OpenMPTarget"
	if (strncmp(handle.name, "OpenMPTarget", 12) == 0) return SPACE_OMPT;
	// check that name starts with "HIP"
	if (strncmp(handle.name, "HIP", 3) == 0) return SPACE_HIP;
	if (strcmp(handle.name, "Host") == 0) return SPACE_HOST;

	abort();
	return SPACE_HOST;
	}

	json_t* gpu_value = json_object_get(power_gpu_watts, "GPU_1");
	json_t* gpu_value = json_object_get(power_gpu_watts, "GPU_" + std::to_string(gdevID));

		output = " Energy Estimation " + std::to_string(((power1 + power2) / 2) *
		((temp - time1) * .001));

	global_kernel_name = std::string(name);
	global_kernel_name = name;

		json_t* my_power_obj = nullptr;
		my_power_obj = json_object();

	json_t* my_power_obj = nullptr;
	my_power_obj = json_object();
	json_t* my_power_obj = json_object();

	if(DEFINED ENV{VARIORUM_ROOT})
	set(Variorum_ROOT $ENV{VARIORUM_ROOT})
	set(MSG_NOTFOUND "check VARIORUM_ROOT environment variable ($ENV{VARIORUM_ROOT})")

Conversation

twilk10 commented Jul 19, 2024

Uh oh!

masterleinad commented Jul 19, 2024

Uh oh!

masterleinad left a comment

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

masterleinad commented Jul 19, 2024

Uh oh!

vlkale commented Jul 19, 2024

Uh oh!

twilk10 commented Jul 19, 2024

Uh oh!

vlkale commented Jul 20, 2024

Uh oh!

twilk10 commented Jul 20, 2024

Uh oh!

vlkale commented Jul 23, 2024

Uh oh!

vlkale commented Jul 23, 2024

Uh oh!

twilk10 commented Jul 23, 2024

Uh oh!

twilk10 commented Jul 23, 2024

Uh oh!

twilk10 commented Jul 23, 2024

Uh oh!

vlkale commented Jul 23, 2024

Uh oh!

twilk10 commented Jul 23, 2024

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

twilk10 commented Aug 6, 2024

Uh oh!

Rombur commented Aug 6, 2024

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!