Weird, take a look at: http://jnaudin.free.fr/lifters/act/html/omptv1.htm"On January 31, 2002, the NASA patent application US2002012221 " Apparatus and Method for generating a thrust using a two dimensional asymmetrical capacitor module " has been granted."Looks alot like a shawyer frustum...
Quote from: rfmwguy on 06/30/2015 12:40 amWeird, take a look at: http://jnaudin.free.fr/lifters/act/html/omptv1.htm"On January 31, 2002, the NASA patent application US2002012221 " Apparatus and Method for generating a thrust using a two dimensional asymmetrical capacitor module " has been granted."Looks alot like a shawyer frustum...From the article:The dielectric material of a capacitor under high voltage experiences a force. Based on the geometry of the capacitor, its material properties, and ambient conditions, the force can be predicted and utilized to move the entire capacitor and its mounting in a predictable direction.Are there any parts of the EM drive that may act as a high voltage capacitor?
@deuteragenie Thanks again for finding that tool. It's very similar to what I have been using. The command that seems to work for me ish5totxt -t 325 -0 -x -49 -o ./NSF-1701-work-h5-data/ez-final-base.csv ./NSF-1701-work-h5-data/ez.h5Of course we will find out as soon as someone starts to look at the data. So all you data reduction gurus, have a ball.https://drive.google.com/folderview?id=0B1XizxEfB23tfnEyQ3l2b053cWFaUGxBcGhDb3FXdFZBbkhSaGtZR3RTd0F5THdvd1oxeWM&usp=sharingThere are 6 .csv files of the big end base view at the end of the run. As such they are small files, 250 kB compared to the Meep output .h5 files of 2.9 GB each. I could attach them here, they are small enough, but by putting them on Google drive they are safe from moving up thread. Just save the link. The folder is in the NSF-1701 folder so maybe the old link will work to access them.
Quote from: aero on 06/30/2015 04:23 pm@deuteragenie Thanks again for finding that tool. It's very similar to what I have been using. The command that seems to work for me ish5totxt -t 325 -0 -x -49 -o ./NSF-1701-work-h5-data/ez-final-base.csv ./NSF-1701-work-h5-data/ez.h5Of course we will find out as soon as someone starts to look at the data. So all you data reduction gurus, have a ball.https://drive.google.com/folderview?id=0B1XizxEfB23tfnEyQ3l2b053cWFaUGxBcGhDb3FXdFZBbkhSaGtZR3RTd0F5THdvd1oxeWM&usp=sharingThere are 6 .csv files of the big end base view at the end of the run. As such they are small files, 250 kB compared to the Meep output .h5 files of 2.9 GB each. I could attach them here, they are small enough, but by putting them on Google drive they are safe from moving up thread. Just save the link. The folder is in the NSF-1701 folder so maybe the old link will work to access them.For example, ex-final-base is a perfectly symmetric square array (106 by 106 entries) of very small numbers (see image attached below).Maximum value of this matrix = 3.78981*10^-8Minimum value of this matrix = -3.78981*10^-8The data histogram (after flattening the matrix) shows it to have a perfectly symmetric distribution as shown below, centered around a value of zero.We need you to disclose the formatting. What is the meaning of the 106 by 106 entries in the array?What is your Finite Difference Grid Mesh? How many FD grid points in the y axis? in the z axis? Are the FD grid points spaced uniformly apart ?
Quote from: aero on 06/30/2015 04:23 pm@deuteragenie Thanks again for finding that tool. It's very similar to what I have been using. The command that seems to work for me ish5totxt -t 325 -0 -x -49 -o ./NSF-1701-work-h5-data/ez-final-base.csv ./NSF-1701-work-h5-data/ez.h5Of course we will find out as soon as someone starts to look at the data. So all you data reduction gurus, have a ball.https://drive.google.com/folderview?id=0B1XizxEfB23tfnEyQ3l2b053cWFaUGxBcGhDb3FXdFZBbkhSaGtZR3RTd0F5THdvd1oxeWM&usp=sharingThere are 6 .csv files of the big end base view at the end of the run. As such they are small files, 250 kB compared to the Meep output .h5 files of 2.9 GB each. I could attach them here, they are small enough, but by putting them on Google drive they are safe from moving up thread. Just save the link. The folder is in the NSF-1701 folder so maybe the old link will work to access them.Progress ! Would it be possible for you to load the final .h5 file or is it too big ? That will allow everyone to try to extract the data as wished.
Quote from: Rodal on 06/30/2015 04:59 pmQuote from: aero on 06/30/2015 04:23 pm@deuteragenie Thanks again for finding that tool. It's very similar to what I have been using. The command that seems to work for me ish5totxt -t 325 -0 -x -49 -o ./NSF-1701-work-h5-data/ez-final-base.csv ./NSF-1701-work-h5-data/ez.h5Of course we will find out as soon as someone starts to look at the data. So all you data reduction gurus, have a ball.https://drive.google.com/folderview?id=0B1XizxEfB23tfnEyQ3l2b053cWFaUGxBcGhDb3FXdFZBbkhSaGtZR3RTd0F5THdvd1oxeWM&usp=sharingThere are 6 .csv files of the big end base view at the end of the run. As such they are small files, 250 kB compared to the Meep output .h5 files of 2.9 GB each. I could attach them here, they are small enough, but by putting them on Google drive they are safe from moving up thread. Just save the link. The folder is in the NSF-1701 folder so maybe the old link will work to access them.For example, ex-final-base is a perfectly symmetric square array (106 by 106 entries) of very small numbers (see image attached below).Maximum value of this matrix = 3.78981*10^-8Minimum value of this matrix = -3.78981*10^-8The data histogram (after flattening the matrix) shows it to have a perfectly symmetric distribution as shown below, centered around a value of zero.We need you to disclose the formatting. What is the meaning of the 106 by 106 entries in the array?What is your Finite Difference Grid Mesh? How many FD grid points in the y axis? in the z axis? Are the FD grid points spaced uniformly apart ?I attach contour plots of ex and hy with numerical values (of whatever this symmetric square matrix is supposed to be )Where is Waldo ?
Quote from: deuteragenie on 06/30/2015 05:26 pmQuote from: aero on 06/30/2015 04:23 pm@deuteragenie Thanks again for finding that tool. It's very similar to what I have been using. The command that seems to work for me ish5totxt -t 325 -0 -x -49 -o ./NSF-1701-work-h5-data/ez-final-base.csv ./NSF-1701-work-h5-data/ez.h5Of course we will find out as soon as someone starts to look at the data. So all you data reduction gurus, have a ball.https://drive.google.com/folderview?id=0B1XizxEfB23tfnEyQ3l2b053cWFaUGxBcGhDb3FXdFZBbkhSaGtZR3RTd0F5THdvd1oxeWM&usp=sharingThere are 6 .csv files of the big end base view at the end of the run. As such they are small files, 250 kB compared to the Meep output .h5 files of 2.9 GB each. I could attach them here, they are small enough, but by putting them on Google drive they are safe from moving up thread. Just save the link. The folder is in the NSF-1701 folder so maybe the old link will work to access them.Progress ! Would it be possible for you to load the final .h5 file or is it too big ? That will allow everyone to try to extract the data as wished.Well, anything is possible but some things are less practical than others. There are 6 final .h5 files, Ex, Ey, Ez, Hx, Hy and Hz. Each of them are 2.9 GB and when zipped all together still nearly 12 GB. I estimate this would take over 16 hours to upload. We need to reach a consensus on what I can do to reduce the data set. The 2.9GB files have 10 views per cycle. Reducing to 1 view per cycle should reduce the output to about 290 MB, still large, but a much more convenient size to transmit over the Internet. Reducing the output to only 4 views per cycle would still more than halve the size, which would be a big help for moving the data around. This is a problem that needs to be solved. I already have a fast cable Internet connection so going faster isn't a good answer. And for general investigation working with the .h5 data, I don't know that all of those time slices add very much.
Quote from: Fractal on 06/30/2015 04:37 pmQuote from: rfmwguy on 06/30/2015 12:40 amWeird, take a look at: http://jnaudin.free.fr/lifters/act/html/omptv1.htm"On January 31, 2002, the NASA patent application US2002012221 " Apparatus and Method for generating a thrust using a two dimensional asymmetrical capacitor module " has been granted."Looks alot like a shawyer frustum...From the article:The dielectric material of a capacitor under high voltage experiences a force. Based on the geometry of the capacitor, its material properties, and ambient conditions, the force can be predicted and utilized to move the entire capacitor and its mounting in a predictable direction.Are there any parts of the EM drive that may act as a high voltage capacitor?Your primary error is to believe what appears on Naudin's website.
To plot on a meaningful basis, one needs the output to be associated with the x,y,z coordinates of each FD grid point location associated with the field vector component.For example:{{Ex1,{ x1, y1, z1}}, {Ex2,{ x2, y2, z2}}.......}Having field vector component data without an association as to what gridpoints it is attached to, and the coordinates of those gridpoints, would be useful only for a square grid FD mesh of equally spaced FD gridpoints.
Quote from: Rodal on 06/30/2015 06:29 pmTo plot on a meaningful basis, one needs the output to be associated with the x,y,z coordinates of each FD grid point location associated with the field vector component.For example:{{Ex1,{ x1, y1, z1}}, {Ex2,{ x2, y2, z2}}.......}Having field vector component data without an association as to what gridpoints it is attached to, and the coordinates of those gridpoints, would be useful only for a square grid FD mesh of equally spaced FD gridpoints.The .csv files contain end views (y-z plane, with x= -49 being the axial coordinate and t = 325, the time coordinate) of the computational lattice with the zero point centered. From this view, the lattice appears to be square, 106 x 106 uniformly spaced pixels counting both edges. That corresponds to 0.3168268537142857 x 0.3168268537142857 meters, so the pixel separation is about 0.002988933 meters, ~ 3 mm. That is much more separation than I would like but you know my issues with resolution. I could increase resolution some, but not a lot.edit x = -49
@Dr. RodalWould you like for me to change my coordinate system to make the z axis the axis of rotation? I could do that, most likely it would be quick, but I won't re-run the data that I have already uploaded so you would need to remember which runs are calculated with "image" coordinates and which runs are calculated with "physics conventions."