Nov. 27, 2023, 2:11 p.m. |
Added
35
|
{"external_links": []}
|
|
Nov. 20, 2023, 2:02 p.m. |
Added
35
|
{"external_links": []}
|
|
Nov. 13, 2023, 1:32 p.m. |
Added
35
|
{"external_links": []}
|
|
Nov. 6, 2023, 1:30 p.m. |
Added
35
|
{"external_links": []}
|
|
Aug. 14, 2023, 1:30 p.m. |
Added
35
|
{"external_links": []}
|
|
Aug. 7, 2023, 1:31 p.m. |
Added
35
|
{"external_links": []}
|
|
July 31, 2023, 1:33 p.m. |
Added
35
|
{"external_links": []}
|
|
July 24, 2023, 1:34 p.m. |
Added
35
|
{"external_links": []}
|
|
July 17, 2023, 1:33 p.m. |
Added
35
|
{"external_links": []}
|
|
July 10, 2023, 1:25 p.m. |
Added
35
|
{"external_links": []}
|
|
July 3, 2023, 1:26 p.m. |
Added
35
|
{"external_links": []}
|
|
June 26, 2023, 1:25 p.m. |
Added
35
|
{"external_links": []}
|
|
June 19, 2023, 1:26 p.m. |
Added
35
|
{"external_links": []}
|
|
June 12, 2023, 1:28 p.m. |
Added
35
|
{"external_links": []}
|
|
June 5, 2023, 1:32 p.m. |
Added
35
|
{"external_links": []}
|
|
May 29, 2023, 1:27 p.m. |
Added
35
|
{"external_links": []}
|
|
May 22, 2023, 1:28 p.m. |
Added
35
|
{"external_links": []}
|
|
May 15, 2023, 1:30 p.m. |
Added
35
|
{"external_links": []}
|
|
May 8, 2023, 1:36 p.m. |
Added
35
|
{"external_links": []}
|
|
May 1, 2023, 1:27 p.m. |
Added
35
|
{"external_links": []}
|
|
April 24, 2023, 1:33 p.m. |
Added
35
|
{"external_links": []}
|
|
April 17, 2023, 1:29 p.m. |
Added
35
|
{"external_links": []}
|
|
April 10, 2023, 1:25 p.m. |
Added
35
|
{"external_links": []}
|
|
April 3, 2023, 1:25 p.m. |
Added
35
|
{"external_links": []}
|
|
Jan. 28, 2023, 11:08 a.m. |
Created
43
|
[{"model": "core.projectfund", "pk": 23121, "fields": {"project": 302, "organisation": 2, "amount": 0, "start_date": "2019-09-30", "end_date": "2023-03-30", "raw_data": 36555}}]
|
|
Jan. 28, 2023, 10:51 a.m. |
Added
35
|
{"external_links": []}
|
|
April 11, 2022, 3:44 a.m. |
Created
43
|
[{"model": "core.projectfund", "pk": 15218, "fields": {"project": 302, "organisation": 2, "amount": 0, "start_date": "2019-09-30", "end_date": "2023-03-30", "raw_data": 854}}]
|
|
April 11, 2022, 3:44 a.m. |
Created
41
|
[{"model": "core.projectorganisation", "pk": 57989, "fields": {"project": 302, "organisation": 109, "role": "LEAD_ORG"}}]
|
|
April 11, 2022, 3:44 a.m. |
Created
40
|
[{"model": "core.projectperson", "pk": 35625, "fields": {"project": 302, "person": 253, "role": "STUDENT_PER"}}]
|
|
April 11, 2022, 3:44 a.m. |
Created
40
|
[{"model": "core.projectperson", "pk": 35624, "fields": {"project": 302, "person": 259, "role": "SUPER_PER"}}]
|
|
April 11, 2022, 1:46 a.m. |
Updated
35
|
{"title": ["", "Flux Reconstruction for Future High Accuracy Aerospace Design Tools"], "description": ["", "\nIn computational fluid dynamics, higher order-of-accuracy methods have been shown to be at least as, if not significantly more accurate than standard second order accuracy schemes while using significantly less computing power. Therefore, these methods could present opportunities to better model highly complex fluid flows, such as in prime movers or power generation equipment for example, through utilising the fast computer speeds available currently.\n\nHowever, individual processor speeds have not increased substantially in recent years and faster computers are as a result of manufacturers simply increasing the number of processors. This causes a major issue for evaluating fluid flows since the analysis must be split over many processors and a large proportion of computing time is devoted solely to transferring data between different processors rather than on calculations. Higher order methods are particularly susceptible to this and their performance is much poorer when multiple cores are used. For very large jobs, it is a huge issue with maybe only 5% of a computer's processing power actually being used for calculations, so there are severe limitations in using higher order equations in practical fluid dynamic design using both current computing and fluid analysis technology. \n\nFlux Reconstruction (FR) seeks to maintain the benefits of using higher order methods but enable them to make use of computer hardware that is available today. The fluid domain is divided into elements and high order equations are used to solve for the parameter of interest and its flux (rate of movement) within each element. However, because each element is solved individually with no relation to neighbouring elements, the solution is discontinuous through the domain. It is corrected using the calculated flux values at each element interface which is used to 'reconstruct' a continuous solution throughout the domain.\n\nModern fluid analysis packages used in industry are mainly based on the second order equations mentioned previously, which require significantly more computing power to achieve the same level of accuracy as higher order equations. FR provides a means to conduct fluid analysis using these higher order equations while still using current computing technology without the issues associated with transferring data between many processors. It is therefore a novel solution if it can be successfully applied to practical fluid analysis and though some effort has gone into current understanding of the FR method, there are some limitations surrounding its complexity, robustness and applicability to commercial software packages.\n\nThe aim of this PhD is to build on the current understanding of FR, conduct further research and attempt to both resolve some of these issues and improve the efficiency of the method. It can then be determined whether there is potential in developing it into a useful computational fluid dynamics tool for industrial applications. This project is fundamental research, so the direction it takes will be led by results, but likely areas of exploration include developing the methods, and applying them to real problems such as the Navier-Stokes Equations. Typical issues associated with computational fluid dynamics would also need to be addressed throughout the course of the project such as stability and accuracy of the FR method.\n\nThe project is of direct relevance to aerospace companies where highly accurate knowledge of dynamic, highly complex fluid flows is required. Current state-of-the-art technology is used to model these flow fields but it is extremely expensive in both computational and monetary terms. If it proved to be viable, FR could significantly reduce the cost of running simulations on for example gas turbine engines. It would also make it easier to implement turbulence modelling techniques that could lead to revolutionary new designs that cannot currently be used since the results may not be accurate.\n\n"], "extra_text": ["", "\n\n\n\n"], "status": ["", "Active"]}
|
|
April 11, 2022, 1:46 a.m. |
Added
35
|
{"external_links": [850]}
|
|
April 11, 2022, 1:46 a.m. |
Created
35
|
[{"model": "core.project", "pk": 302, "fields": {"owner": null, "is_locked": false, "coped_id": "ce01dc21-67ee-45db-9724-a1ed9d7e4819", "title": "", "description": "", "extra_text": "", "status": "", "start": null, "end": null, "raw_data": 839, "created": "2022-04-11T01:29:19.535Z", "modified": "2022-04-11T01:29:19.535Z", "external_links": []}}]
|
|