eval_details.csv column order

[gnowzil]

We noticed that when a contingency has infeasibilities, the information in the row that is printed to eval_detail.csv is not complete and also gets printed in such a way that the information does not match up to the header.

I did verify this by changing write_summary to print out the header along with each line.

I'm not sure if this is by design, but it did lead to quite a bit of confusion for my team when we were debugging our code.

[GOCompetition]

Hi Elizabeth, Thank you for pointing this out. We will fix this as soon as possible. Best regards, Jesse Holzer From: Stephen Elbert <steve.elbert@gmail.com> Date: Thursday, October 29, 2020 at 11:20 AM To: "Holzer, Jesse T" <jesse.holzer@pnnl.gov> Subject: Fwd: [GOCompetition/C2DataUtilities] eval_details.csv column order (#1) Check twice before you click! This email originated from outside PNNL. Begin forwarded message: From: Elizabeth Wong <notifications@github.com> Date: October 29, 2020 at 11:16:07 PDT To: GOCompetition/C2DataUtilities <C2DataUtilities@noreply.github.com> Cc: Subscribed <subscribed@noreply.github.com> Subject: [GOCompetition/C2DataUtilities] eval_details.csv column order (#1) Reply-To: GOCompetition/C2DataUtilities <reply@reply.github.com> We noticed that when a contingency has infeasibilities, the information in the row that is printed to eval_detail.csv is not complete and also gets printed in such a way that the information does not match up to the header. I did verify this by changing write_summary to print out the header along with each line. I'm not sure if this is by design, but it did lead to quite a bit of confusion for my team when we were debugging our code. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub<https://gcc02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FGOCompetition%2FC2DataUtilities%2Fissues%2F1&data=04%7C01%7Cjesse.holzer%40pnnl.gov%7Ce9ad31736ffa41d01b1708d87c376169%7Cd6faa5f90ae240338c0130048a38deeb%7C0%7C1%7C637395924585591865%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C2000&sdata=zEE6oRj9v7X7RQbVD%2BOLZ2U%2F2FDWrduqBWb1Ha1E5Sk%3D&reserved=0>, or unsubscribe<https://gcc02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAIWLD6MSPDPMQVHGRUI7FVDSNGWOPANCNFSM4TECZ7VQ&data=04%7C01%7Cjesse.holzer%40pnnl.gov%7Ce9ad31736ffa41d01b1708d87c376169%7Cd6faa5f90ae240338c0130048a38deeb%7C0%7C1%7C637395924585601816%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C2000&sdata=5rolnwCD6ytw72FZEkY8aNepaCGIorrU0hKZuIxTBys%3D&reserved=0>.

[GOCompetition]

Hi Elizabeth, This bug is fixed now. Please pull to obtain the fixes. Thanks again for reporting it. Best regards, Jesse Holzer From: "Holzer, Jesse T" <jesse.holzer@pnnl.gov> Date: Saturday, October 31, 2020 at 8:52 AM To: "reply@reply.github.com" <reply@reply.github.com> Cc: Stephen Elbert <steve.elbert@gmail.com>, ^PNNL ARPA Competition Administrator <arpacomp@pnnl.gov> Subject: Re: [GOCompetition/C2DataUtilities] eval_details.csv column order (#1) Hi Elizabeth, Thank you for pointing this out. We will fix this as soon as possible. Best regards, Jesse Holzer From: Stephen Elbert <steve.elbert@gmail.com> Date: Thursday, October 29, 2020 at 11:20 AM To: "Holzer, Jesse T" <jesse.holzer@pnnl.gov> Subject: Fwd: [GOCompetition/C2DataUtilities] eval_details.csv column order (#1) Check twice before you click! This email originated from outside PNNL. Begin forwarded message: From: Elizabeth Wong <notifications@github.com> Date: October 29, 2020 at 11:16:07 PDT To: GOCompetition/C2DataUtilities <C2DataUtilities@noreply.github.com> Cc: Subscribed <subscribed@noreply.github.com> Subject: [GOCompetition/C2DataUtilities] eval_details.csv column order (#1) Reply-To: GOCompetition/C2DataUtilities <reply@reply.github.com> We noticed that when a contingency has infeasibilities, the information in the row that is printed to eval_detail.csv is not complete and also gets printed in such a way that the information does not match up to the header. I did verify this by changing write_summary to print out the header along with each line. I'm not sure if this is by design, but it did lead to quite a bit of confusion for my team when we were debugging our code. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub<https://gcc02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FGOCompetition%2FC2DataUtilities%2Fissues%2F1&data=04%7C01%7Cjesse.holzer%40pnnl.gov%7Ce9ad31736ffa41d01b1708d87c376169%7Cd6faa5f90ae240338c0130048a38deeb%7C0%7C1%7C637395924585591865%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C2000&sdata=zEE6oRj9v7X7RQbVD%2BOLZ2U%2F2FDWrduqBWb1Ha1E5Sk%3D&reserved=0>, or unsubscribe<https://gcc02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAIWLD6MSPDPMQVHGRUI7FVDSNGWOPANCNFSM4TECZ7VQ&data=04%7C01%7Cjesse.holzer%40pnnl.gov%7Ce9ad31736ffa41d01b1708d87c376169%7Cd6faa5f90ae240338c0130048a38deeb%7C0%7C1%7C637395924585601816%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C2000&sdata=5rolnwCD6ytw72FZEkY8aNepaCGIorrU0hKZuIxTBys%3D&reserved=0>.