Commit 9405ea1c384534657d3a4adb62b04bda8c2c7f0b
Exists in
master
and in
3 other branches
Merge branch 'master' of http://128.243.70.77/UoN/SACAMOS
Showing
1 changed file
with
1 additions
and
415 deletions
Show diff stats
SOFTWARE_NOTES/known_problems.txt
| 1 | -1. Section 3 of the theory document is not quite complete - we need to present the full worked through solution | |
| 2 | - and then comment the analytic solution implementation accordingly. | |
| 3 | - STARTED - not yet complete | |
| 4 | - | |
| 5 | -2. Comilation fails on gfortran version 4.4.7 - this version of gfortran does not implement the full f2008 standard | |
| 6 | - and the command EXECUTE_COMMAND_LINE() is not implemented and we have to go back to the old | |
| 7 | - non-standard SYSTEM() command. | |
| 8 | - FINISHED - only compilers which conform to 2008 standard are supported | |
| 9 | - | |
| 10 | -3. At the moment the Latex documentation is difficult to build from the .tex and .cls files. There are fonts and other | |
| 11 | - things missing from the standard Latex installation and other packages are obviously required. Maybe the Latex cls | |
| 12 | - file could be simplified to make it more portable - it seems overly complex at the moment. | |
| 13 | - FIXED: NLR have provided a revised class file for the documents. | |
| 14 | - | |
| 15 | -4. There is a problem with paths in cygwin: | |
| 16 | - pwd gives the form /home/user/ | |
| 17 | - whereas this directory is in fact | |
| 18 | - C:/cygwin64/home/user/ | |
| 19 | - ngspice called from cygwin requires the second form to work correctly | |
| 20 | - | |
| 21 | - FIXED: used cygpath -m ($pwd) to get the path in cygwin. BUT NEED TO CHECK... | |
| 22 | - | |
| 23 | -5. If the code is installed in a directory whose path contains | |
| 24 | - spaces then make fails. Reading around the web the advice appears to be | |
| 25 | - that filenames and directory names with spaces should never be used. | |
| 26 | - Whilst there are some methods for getting around parts of this problem | |
| 27 | - there is no consensus on a solution. | |
| 28 | - | |
| 29 | - NO FURTHER ACTION: The advice at the moment is not to install the code in a path that contains spaces. | |
| 30 | - | |
| 31 | -6. In cygwin any underscore characters are interpreted as indicating a | |
| 32 | - following subscript character. We need to explicity set the terminal settings | |
| 33 | - to stop this i.e. we need something like the following in gnuplot files: | |
| 34 | - set term x11 noenhanced | |
| 35 | - | |
| 36 | - FIXED | |
| 37 | - | |
| 38 | -7. There is a problem with transient analysis in NGspice. Ngspice fails for long simulation | |
| 39 | -times. Options to proceed: | |
| 40 | -a. We can look at the simulation parameters and their effect on the transient simulation | |
| 41 | -s. We can try to replace the simple delay line with an equivalent LTRA transmission line | |
| 42 | - model which is implemented in a different way and could be more robust | |
| 43 | -c. Ask advice on the ngspice user forum. | |
| 44 | - IN_PROGRESS: This issue was raised in the phase 1 test cases which had a fixed spice model | |
| 45 | - topology. If a s-domain transfer function was not required (H(jw)=1) then this was implemented | |
| 46 | - as a single pole model where the pole was placed at extremely high frequency. This | |
| 47 | - pole can cause a problem. | |
| 48 | - | |
| 49 | - STARTED: The original issue was with the s-domain transfer function for frequency independent | |
| 50 | - test cases in the original Phase_1 test cases. The s-domain transfer function was included whether | |
| 51 | - needed or not. If not needed then the s-domain transfer function consisted of a single pole at | |
| 52 | - a very high frequency. This pole is what causes the problem. Shifting the pole frequency allows | |
| 53 | - the simulation to proceed for longer. | |
| 54 | - In the software code we only include s-domain transfer functions where required. Maybe | |
| 55 | - we should also consider a constraint on the position of poles in the s-plane... | |
| 56 | - | |
| 57 | - As at 13th June 2016 this issue appears to occur very frequently. Initial investigations at NLR | |
| 58 | - suggest that this is limited to ngspice and does not occur in LTspice or Pspice. | |
| 59 | - Some of the solution parameters and tolerances *(see 18) can have an effect on whether the solution completes or at | |
| 60 | - least the length of time it runs before failure. | |
| 61 | - The use of LTRA models doesn't improve the robustness of the solution and it still fails. | |
| 62 | - | |
| 63 | - REQUIRES FURTHER WORK: This issue can be addressed by the implementation of the s-domain transfer functions using | |
| 64 | - passive networks (note this will also improve the portability of the software, no differences between Ngspice, LTspice or Pspice. | |
| 65 | - | |
| 66 | - STARTED: The original issue was with the s-domain transfer function for frequency independent | |
| 67 | - test cases in the original Phase_1 test cases. The s-domain transfer function was included whether | |
| 68 | - needed or not. If not needed then the s-domain transfer function consisted of a single pole at | |
| 69 | - a very high frequency. This pole is what causes the problem. Shifting the pole frequency allows | |
| 70 | - the simulation to proceed for longer. | |
| 71 | - In the final code we should only include s-domain transfer functions where required and maybe | |
| 72 | - we should consider a constraint on the position of poles in the s-plane. | |
| 73 | - | |
| 74 | -8. The validation examples use VM(node) for both a.c. and transient analysis. This needs to be | |
| 75 | - checked and changed if required as we don't want |V| output for transient analysis... | |
| 76 | - DONE | |
| 77 | - | |
| 78 | -9. PSpice does not understand the output VM(node) (this is used to request voltage magnitude output in | |
| 79 | - ngspice and Ltspice.) | |
| 80 | - DONE: Spice versions have their own circuit files. | |
| 81 | - | |
| 82 | -10. Cannot model shielded cables without a ground plane at the moment i.e. we assume that there is always | |
| 83 | - as external domain and this is not necessarily the case. | |
| 84 | - FIXED - see test case COAX | |
| 85 | - | |
| 86 | -11. The domain decompositon process implementation in the cable_bundle_model_builder is very messy. This need | |
| 87 | - to be re-worked thoroughly - a new notation needs to be developed and the software linked to the theory document for | |
| 88 | - this aspect of the solution. | |
| 89 | - DONE but still somewhat complicated so this could still be looked at again... | |
| 90 | - | |
| 91 | -12. Over-shields have not been implemented yet... | |
| 92 | - DONE | |
| 93 | - | |
| 94 | -13. Discrepancy in mutual inductance vs NLR for TWO_WIRES_OVER_GROUND_PLANE_MOD test case | |
| 95 | - Fixed 30/3/2016 CJS. Formula implemented wrongly - factor of 2 out... | |
| 96 | - | |
| 97 | -14. There are some fixed format write statements which may cause problems if spice circuit element names become too long. See write_filter_model() for example. | |
| 98 | - STARTED: we have extended the format so that it deals with any proactical situation | |
| 99 | - | |
| 100 | -15. The eigenvector/ eigenvalue solver fails to return an accurate result for some configurations (Spacewire with the same dielectric throughout (air) for example). This problem needs serious attention. | |
| 101 | - STARTED: The Spice model is now derived using a rigorous method based on eigensolutions of real, symmetric matrices. There may still | |
| 102 | - be an issue with the analytic solution which requires the diagonalisation of a complex general matrix at every frequency of analysis. | |
| 103 | - The complex diagonalisation method now includes a very small perturbation to the diagonal elements of the matrix which | |
| 104 | - prevents the degenerate mode problem from ocurring - need to check that this is consistent with the modal decomposition for the lossless case i.e. that the modes found will be the same... | |
| 105 | - | |
| 106 | -16. There can be a failure to consistently identify a particular mode when deriving the correction function This leads to problems | |
| 107 | - with the filter fitting. Maybe we need to investigate a method by which the high frequency modes (eigenvectors) are used to generate mode propagation constants at each frequency in an iterative approach... It is also important for the propagation correction that the modes are consistent over the whole frequency range of the simmulation. At the moment this is a matter of relying on eispack to achieve this but it MUST be imposed explicitly in the software. | |
| 108 | - STARTED: We now order the eigenvalues and use this ordering to uniquely identify modes. Degenerate modes are not a problem as | |
| 109 | - only eigenvalues are used in deriving the propagation correction. | |
| 110 | - DONE 27/10/2016. This process has been given some more rigor now: The modes are identified by calculating the overlap between the reference | |
| 111 | - (lossless) configuration modes and the locally calculated modes. | |
| 112 | - | |
| 113 | -17. The frequency range used for the propagation correction needs to be sorted out properly. It is arranged on the basis | |
| 114 | - of the validation test case frequency range (or the frequency range required in FFT for transient solution) | |
| 115 | - STARTED: The frequency range for filter fitting may now be set explicitly in the .spice_model_spec file. | |
| 116 | - DONE: the The frequency range for filter fitting has now been extended to the Yfilter matrix calculation process. | |
| 117 | - | |
| 118 | -18. There can be a problem with convergence of the s-domain transfer function solution in transient simulations. | |
| 119 | - The stopping point is affected by: voltage source function (including amplitude) and options RELTOL,CONVABSSTEP,CHGTO in non-obvious ways. | |
| 120 | - UNDER INVESTIGATION: This appears to be a problem with the Ngspice implementation of s-domain transfer functions. An alternative | |
| 121 | - based on network synthesis of the transfer function is being investigated as an alternative. | |
| 122 | - SEE POINT 7. | |
| 123 | - | |
| 124 | -19. The conductor impedance modelling code needs its own module separate from the cable module I think as it is used everywhere. | |
| 125 | - | |
| 126 | -20. The transfer impedance model code includes a large amount of repeated code for the special case Ts=Tv which requires a | |
| 127 | - different circuit. | |
| 128 | - DONE: the implementation of this special case has been updated. | |
| 129 | - | |
| 130 | -21. There is a small discrepancy between ZT_WIRE_WITH_OVERSHIELD_AND_SINGLE_WIRE ZT_FD_COAX_AND_SINGLE_WIRE_FREE_SPACE | |
| 131 | - which should be the same test case but set up in different ways. This should be resolved or at least understood. | |
| 132 | - FINISHED: This was resolved in development of the transfer impedance model to multi-mode propagation. | |
| 133 | - | |
| 134 | -22. The frequency calculation for log and linear scales needs to be tidied up as it is repeated in several places... | |
| 135 | - STARTED with GENERAL_MODULES/frequency_spec.F90:TYPE :: frequency_specification | |
| 136 | - but this needs to be used everywhere. | |
| 137 | - DONE | |
| 138 | - | |
| 139 | -23. The writing of comments in the spice circuit file should be done in a subroutine to reduce the size of the code | |
| 140 | - and would allow an easy change to the style of comments | |
| 141 | - STARTED with write_spice_method_of_characteristics_equivalent_circuit.F90 | |
| 142 | - DONE. | |
| 143 | - | |
| 144 | -24. The allocation of new node numbers should be done in a subroutine to reduce the size of the code | |
| 145 | - STARTED - needs to be used everywhere now. | |
| 146 | - DONE | |
| 147 | - | |
| 148 | -25. The summation terms in the transfer impedance model are implemented with series voltage sources. It may be | |
| 149 | - better to use current sources and a 1 ohm resistance to implement the sum as this will reduce the node count. | |
| 150 | - | |
| 151 | -26. The filter fit should use the best available model, not simply the highest order model. | |
| 152 | - DONE 30/6/2016 | |
| 153 | - | |
| 154 | -27. The transfer impedance model needs thorough testing for cases when the shield whose transfer impedance we are | |
| 155 | - including in the model is and is not the reference conductor in the source/ victim domain. | |
| 156 | - STARTED: SEE ADDITIONAL_TEST_CASES | |
| 157 | - DONE | |
| 158 | - | |
| 159 | -28. Reordering the conductors in the FOUR_WIRE_BUNDLE test case can cause a difference in results: Is this related | |
| 160 | - to the eigenvector problem? Why is there an error in the zero order filter fitting in this lossless case? | |
| 161 | - This needs to be investigated and solved. | |
| 162 | - DONE: This was fixed with the implemetation of the improved (rigorous) eigensolver for the spice model | |
| 163 | - modal decomposition. | |
| 164 | - | |
| 165 | -29. We need to check whether we have more components than necessary in the transfer impedance model. We have | |
| 166 | - one source mode delays for each victim mode. | |
| 167 | - | |
| 168 | -30. Make clear how the reference conductor is specified in the user guide. | |
| 169 | - DONE: There is now a short section in the user guide relating to this issue. | |
| 170 | - | |
| 171 | -31. Transient solution bug if order of filter fitting model and frequency range is not specified. Filter fitting doesn't seem to | |
| 172 | - get a testing frequency list... This is due to moving the analytic solution to after the spice model creation and also realtes | |
| 173 | - to the frequency range specification issue (nummber 22) | |
| 174 | - DONE: Frequency range for filter fitting is specified explicitly now for these test cases. | |
| 175 | - | |
| 176 | -32. 20/6/2016 FD_LARGE_BUNDLE test case gives poor results for 20 conductors with a propagation correction included (but OK with no propagation correction). I think the first thing to look at are some of the convergence (and other solution) parameters in Ngspice. | |
| 177 | - Note that it appears to work in LTspice. | |
| 178 | - STARTED: This has been accepted as shoowing a problem with Ngspice. Note that replacing the s-domain transfer functions with an equivalent circuit | |
| 179 | - implementation of the propagation correction gives the correct result in Ngspice. | |
| 180 | - SEE POINT 7. | |
| 181 | - | |
| 182 | -33. SUBROUTINE write_Pspice_filter_model has three different forms of output for testing with Pspice, LTspice. It appears that the | |
| 183 | - third form with explicit normalisation of coefficients works the best but this needs thorough testing, including with Pspice | |
| 184 | - before the un-used formats are stripped out. | |
| 185 | - DONE | |
| 186 | - | |
| 187 | -34. Problem with a0=b0=0 in transfer impedance filters in LTspice. This is die to subtracting the d.c. resistance then integrating in time | |
| 188 | - (multiplying by 1/s in Laplace domain) | |
| 189 | - DONE: Fixed: Divide top and bottom by s before writing the ZT filters in SUBROUTINE write_transfer_impedance_circuit | |
| 190 | - | |
| 191 | -35. At the moment conductors can be placed on both sides of a ground plane, also the incident field excitation is symmetrical wrt to the | |
| 192 | - ground plane i.e. there is field on both sides. I think we need to check where the conductors are wrt the ground plane. | |
| 193 | - DONE. | |
| 194 | - | |
| 195 | -36. Check the assumptions about the termination configuration in both the Spice model and the analytic model to make sure | |
| 196 | - that they are consistent. This needs to be documented thoroughly. | |
| 197 | - DONE. I think the models are consistent and the comparisons between the analytic and Spice models show this for a range of incident angles. | |
| 198 | - | |
| 199 | -37. The mesh format translation in Laplace.F90 is not the most efficient and may be simplified. | |
| 200 | - DONE | |
| 201 | - | |
| 202 | -38. We need to decide how to calculate the L/C/G matrices for the twisted pair model as we assume | |
| 203 | - a common mode/ differential mode decomposition i.e. how do we calculate the L/C/G for the common mode | |
| 204 | - only? | |
| 205 | - DONE We use an equivalent radius (specified as a parameter) which provides good agreement with the NLR averaging method. | |
| 206 | - | |
| 207 | -39. A single oversheild (empty) over a ground plane fails with the error: | |
| 208 | - ERROR in PUL_LC_calc_overshield_wide_separation_approximation | |
| 209 | - Conductor lies outside or intersects the reference shield conductor | |
| 210 | - DONE: create_global_domain_structure.F90 was assuming that all overshields contributed a viable domain i.e. they had internal conductors. | |
| 211 | - for this test case the overshield is empty and therefore | |
| 212 | - | |
| 213 | -40. The analytic solution for shielded cables appears to work if we assume that all shielded conductors are at the same position in space | |
| 214 | - as the shield but this needs to be justified properly in the theory manual (or not...) | |
| 215 | - This solution will probably fail for overshield domains... Maybe we need to shift all conductors within an overshield to the overshield centre | |
| 216 | - for the purposes of incident field calculation. | |
| 217 | - STARTED: The position of shielded conductors is shifted as described and the tests so far work. This needs justification. | |
| 218 | - DONE: This model does appear to work but we have also explicitly set the current source term IF to zero in shielded domains in the analytic solution. | |
| 219 | - This gives good comparisons between Spice and analytic models, especially when using the full model of Xie. | |
| 220 | - | |
| 221 | -41. How does the analytic solution deal with the domain decomposition model for twisted pairs? Does it get it right? | |
| 222 | - STARTED: see point 43 and comparisons between spice and analytic solutions, especially regarding loss models at low frequency | |
| 223 | - DONE. No discrepancies now seen in the test cases. | |
| 224 | - | |
| 225 | -42. The Laplace solver assumes epsr=1 in the 'free space' region however it can take other values for internal domains for spacewire, twinax and | |
| 226 | - shielded twisted pairs. We need to include a 'free space' dielectric constant in the PUL structure and via this into Laplace. | |
| 227 | - DONE | |
| 228 | - | |
| 229 | -43. How does the common mode/ differential mode decomposition for twisted pairs work with the conductor based loss model? I'm not sure that it is rigorous and needs to be checked. | |
| 230 | - Error with the allocation of conductor losses for twisted pairs. In the analytic solution | |
| 231 | - the domain based common mode/ differential mode decomposition was in error as the common mode | |
| 232 | - sees the two conductors in parallel. The losses in twisted pair and shielded twisted pair cables needs | |
| 233 | - proper investigation. This has an impact in propagation_correction_filters.F90 frequency_domain_analysis.F90 | |
| 234 | - and time_domain_analysis.F90 as well as conductor_impedance_model.F90 | |
| 235 | - | |
| 236 | - 8/9/2016: Attempted fix using conductor_impedance%Resistance_multiplication_factor to get the common mode/ | |
| 237 | - differential mode loss contributions correct in both the spice model propagation correction and | |
| 238 | - the analytic solution. NEEDS MORE TESTING... | |
| 239 | - DONE | |
| 240 | - | |
| 241 | -44. Lines longer than 132 characters cause an error in Pspice. | |
| 242 | -STARTED: Node number lists at either end are on separate lines with fixed format (I6) integers. | |
| 243 | -Note that this is not yet general as the line length can be greater than 132 characters in the number of conductors > 22 | |
| 244 | -DONE 10/10/2016. SUBROUTINE write_long_node_list should prevent this problem from occurring | |
| 245 | - | |
| 246 | -45. Probably need to implement a file for warnings e.g. inaccurate filter fits etc during the model creation process or | |
| 247 | - transfer impedance and surface impedance of a shield are not equal at d.c. This | |
| 248 | - will alert the user to potential problems even if a working spice model is produced. | |
| 249 | - | |
| 250 | -46. Do we need to integrate the shield model (transfer impedance and shield conductor impedance) creation process into the | |
| 251 | - automatic testing script? At the moment there is some test data in the TEST_CASES directory but this is not run automatically. | |
| 252 | - | |
| 253 | -47. There is an error in the domain decomposition matrices for the twisted pair model when a twisted pair is in a bundle | |
| 254 | - with other conductors. This causes coupling from the differential mode onto other cables. | |
| 255 | - STARTED: The error originates from the construction of the MV and MI matrices on a domain basis. Elements of MV and MI are | |
| 256 | - overwritted when the external domain is defined. The fix is to check whether a conductor is a reference conductor for another | |
| 257 | - domain before overwriting it. Reference conductors should already have their MV and MI matrix elements set correctly. | |
| 258 | - This needs thorough checking. Also need to check that it is correct in overshield domains. | |
| 259 | - SUBROUTINE create_global_domain_structure has been updates so this should no longer be a problem... | |
| 260 | - DONE | |
| 261 | - | |
| 262 | -48. There is the possibility that the problem could be a single domain which is shielded so check for this | |
| 263 | - We need to implement a check as to whether the last viable domain is an external domain | |
| 264 | - There is the possibility that the last domain is shielded so no differential mode can be excited by the incident field | |
| 265 | - DONE | |
| 266 | - | |
| 267 | -49. The incident field excitation documentation is based on Clayton Paul's derivation. Maybe it is too close and needs | |
| 268 | -to be reworded and a different notation adopted? | |
| 269 | - | |
| 270 | -50. Elements of TVI used in the transfer impedance model were wrongly transposed in SUBROUTINE write_transfer_impedance_circuit | |
| 271 | - Tjis was found while writing the documentation for this part of the model. | |
| 272 | -DONE: | |
| 273 | -!OLD TVI_victim_row(1:n_victim_domain_modes)=TVI_victim(victim_domain_shield_conductor,1:n_victim_domain_modes) | |
| 274 | -! NEW | |
| 275 | - TVI_victim_row(1:n_victim_domain_modes)=TVI_victim(1:n_victim_domain_modes,victim_domain_shield_conductor) | |
| 276 | - | |
| 277 | -51. We need to give user control over the filter fitting parameters for the PUL parameters - this is hard wired at the moment. | |
| 278 | - DONE | |
| 279 | - | |
| 280 | -52. Spacewire models use common mode/ differential mode decomposition but this is not implemented rigorously for frequency dependent dielectrics- | |
| 281 | - it is assumed that the dielecric is homogeneous in the shielded twisted pairs. | |
| 282 | - STARTED: 2/10/2016 done for inhomogeneous but constant dielectrics | |
| 283 | - | |
| 284 | -53. Conductor shape paramters are set in more than one place (PUL and CABLE_MODULE PUL_LC_ground_plane.F90 | |
| 285 | - PUL_LC_overshield.F90 and PUL_LC_open_boundary.F90) need to rationalise this | |
| 286 | - DONE | |
| 287 | - | |
| 288 | -54. Can we combine PUL_LC_ground_plane.F90 PUL_LC_overshield.F90 and PUL_LC_open_boundary.F90 ? | |
| 289 | - DONE 13/12/2016 | |
| 290 | - | |
| 291 | -55. external conductor information should have it's own structure I think... This should allow us to remove the horrible fix | |
| 292 | - for flex cables which have to have their conductor offsets calculated in create_global_domain_structures.F90. | |
| 293 | - DONE. 6/10/2016 | |
| 294 | - | |
| 295 | -56. Need to implement the conductor loss model for rectangular conductors. | |
| 296 | - DONE 10/10/2016 | |
| 297 | - | |
| 298 | -57. We need to test reordering of conductors - especially when shields may or may not be reference conductors. | |
| 299 | - STARTED: See ADDITIONAL_TEST_CASES especially some of the transient simulations. | |
| 300 | - DONE | |
| 301 | - | |
| 302 | -58. Are the results of the incident field excitation model dependent on the | |
| 303 | -conductor numbering i.e. the choice of the reference conductor? | |
| 304 | -The integration paths/ areas are between conductor and reference conductor... | |
| 305 | -STARTED: This has been looked at in: ADDITIONAL_TEST_CASES/THREE_WIRE_RIBBON_CABLE_EINC | |
| 306 | -where there are only small differences when the conductors are re-ordered. | |
| 307 | -DONE: All discrepancies have been eliminated for the re-numbered test case. | |
| 308 | - | |
| 309 | -59. We need to deal with the situation when Tvictim=Tsource and Tvictim=Tz in the Xie model. Botched at the moment... | |
| 310 | - DONE 7/10/2016 | |
| 311 | - | |
| 312 | -60. The analytic solution assumes that shielded conductors are at the centre of the shield for incident field excitation... | |
| 313 | - This is not the case for bundles with overshields so this needs fixing... | |
| 314 | - DONE: Shielded conductors take the coordinates of the shield centre for the incident field excitation. This | |
| 315 | - has the effect of there being no voltage or current sources between the shielded cables and the shield. | |
| 316 | - | |
| 317 | -61. Could the ground plane be included as a normal rectangular conductor in the Spice model? | |
| 318 | - | |
| 319 | -62. Problem with transfer impedance test cases from NLR. Found that coax and single wire model changed according to the ordering | |
| 320 | - of conductors i.e. if the coax shield was or was not the reference conductor in the victim domain. | |
| 321 | - DONE: Found a sign error in write_transfer_impedance_circuit.F90 (also repeated in write_ZT_incident_field_excitation_circuit.F90 | |
| 322 | - ! original | |
| 323 | - TVI_victim_row(1:n_victim_domain_modes)=TVI_victim(1:n_victim_domain_modes,victim_domain_shield_conductor) | |
| 324 | - should be: | |
| 325 | - ! sign error found 13/10/2016 | |
| 326 | - TVI_victim_row(1:n_victim_domain_modes)=-TVI_victim(1:n_victim_domain_modes,victim_domain_shield_conductor) | |
| 327 | - | |
| 328 | - Also an error in the analytic solution in adding transfer impedance terms to the Z matrix in some circumstances. | |
| 329 | - | |
| 330 | -63. Error found in the domain decomposition matrix MV for a double shielded coax and single wire over ground. | |
| 331 | - DONE 18/10/2016. This was due to errors in filling MV for the overshield - terms related to the reference | |
| 332 | - conductor in the overshield domain. | |
| 333 | - | |
| 334 | -64. We need to make the surface impedance and transfer impedance consistent. See Jaco's e-mails 20/10/2016. | |
| 335 | - STARTED: by setting thickness, t=0 in the cable_spec file an 'equivalent thickness' is calculated from the | |
| 336 | - transfer impedance at d.c. | |
| 337 | - STILL NEED to deal with the case if sigma=0 or Zt=0 at f=0 for example which will cause an error. | |
| 338 | - DONE | |
| 339 | - | |
| 340 | -65. We generate meshes at the cable model building stage and also at the bundle model building stage. | |
| 341 | - Meshes for both cables and bundles are labeled on a domain basis however there is no distinction between cable internal | |
| 342 | - domain mesh numbers and bundle domain numbers. Do we need to indicate which is which? Do we need all cable and bundle meshes | |
| 343 | - available at the same time? | |
| 344 | - DONE: The meshes have been named with the cable or bundle name as well as the domain number. | |
| 345 | - | |
| 346 | -66. FD_Shielded twisted pair models are calculating the L and C matrices for the common and differential mode using L and C | |
| 347 | - calculated assuming a homogeneous dielectric i.e. rd is ignored... | |
| 348 | - DONE 2/10/2016 | |
| 349 | - | |
| 350 | -67. Need proper checks for conductor/dielectric intersection with a meaningful error message, not just a mesh generation error. | |
| 351 | - STARTED: working for cylindrical conductors but not included for rectangular conductors. | |
| 352 | - DONE April 2017 | |
| 353 | - | |
| 354 | -68. The test for frequency dependent dielectrics fails if epsr(infinty)->1.0 | |
| 355 | - DONE 8/10/2016 Now we check that epsr(f=0).NE.1.0 .OR. the order of the material .NE.0 | |
| 356 | - | |
| 357 | -69. Cable intersection check needs to include rectangular conductors and the ground plane | |
| 358 | - SEE 67. | |
| 359 | - DONE April 2017 | |
| 360 | - | |
| 361 | -70. Check signs in the calculation of G in Laplace with complex epsr. Note that this still requires validation... | |
| 362 | - DONE and consistent with the theory. | |
| 363 | - | |
| 364 | -71. There is a problem with the modal decomposition if an assymetric structure becomes symmetric as w-> infinity | |
| 365 | - as the frequency dependent modal decomposition then does not converge to the w-> infinity decomposition and the | |
| 366 | - propagation correction gets messed up. | |
| 367 | - | |
| 368 | -72. Pspice simulations of some transient test cases take a very long time... This is due to very small delays in incident field excitation model transmission lines for some angles of incidence. | |
| 369 | - DONE: 6/12/2016 Replace small delay transmission lines by a very small resistance. | |
| 370 | - | |
| 371 | -73. Allow command line arguments to all three software modules. | |
| 372 | -e.g. cable_model_builder cable_name | |
| 373 | - DONE | |
| 374 | - | |
| 375 | -74. There is a small loss of accuracy if Ts is approximately equal to Tv for incident field coupling for shielded cables | |
| 376 | - see EINC_ZT_MULTI_MODE_2S_2V. This seems to appear at low frequency where the coupled signal is so low that it is probably insignificant. | |
| 377 | - DONE. This may be dealt with by increasing the minimum transmission line delay parameter in the spice_model_spec file | |
| 378 | - i.e. include the lines: | |
| 379 | -min_delay | |
| 380 | -1E-11 | |
| 381 | - | |
| 382 | - Maybe we could change the default value... | |
| 383 | - | |
| 384 | -75 Incident field excitation of shielded twisted pair fails with the following: | |
| 385 | -1 # order for vector fit model | |
| 386 | -log # frequency scale (log or lin) | |
| 387 | -1e2 1e9 100 # fmin fmax number_of_frequencies | |
| 388 | -use_xie | |
| 389 | -use_high_freq_Zt_model | |
| 390 | -no_s_xfer | |
| 391 | - | |
| 392 | -:Singular matrix error | |
| 393 | - | |
| 394 | -Also fials with: | |
| 395 | - | |
| 396 | -1 # order for vector fit model | |
| 397 | -log # frequency scale (log or lin) | |
| 398 | -1e2 1e9 100 # fmin fmax number_of_frequencies | |
| 399 | -no_Xie | |
| 400 | -use_high_freq_Zt_model | |
| 401 | -no_s_xfer | |
| 402 | - | |
| 403 | -0 # order for vector fit model | |
| 404 | -log # frequency scale (log or lin) | |
| 405 | -1e2 1e9 100 # fmin fmax number_of_frequencies | |
| 406 | -use_high_freq_Zt_model | |
| 407 | -use_Xie | |
| 408 | -no_s_xfer | |
| 409 | - | |
| 410 | -Ithink it may be that the fixed topology equivalent circuit used cannot deal with a pole at zero frequency... | |
| 411 | - | |
| 412 | -76 We see a failure (singular matrix error in ngspice) if we set the two transfer impedance coupling directions to +1 in the test case: ZT_TWIN_COAX_INCIDENT_FIELD_EXCITATION_USE_XIE. | |
| 413 | -DONE: fixed 12/6/2017 | |
| 414 | - | |
| 415 | - | |
| 1 | +Record of known problems in SACAMOS | ... | ... |